Synchronization signal block (ssb) measurement accuracy testing

ABSTRACT

In a general aspect, a user equipment (UE) in a cellular communications network receives a first Synchronization Signal Block (SSB) corresponding to a first cell of the cellular communications network, and a second SSB corresponding to a second cell of the cellular communications network. The UE clarifies a first cell identifier (ID) of the first cell. The UE clarifies a second cell ID of the second cell. The UE determines an SSB measurement accuracy value using the first cell ID and the second cell ID.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims priority to U.S. Provisional Patent ApplicationNo. 62/826,702, filed Mar. 29, 2019, the entire content of which isincorporated herein by reference.

TECHNICAL FIELD

The following disclosure relates generally to the field of wirelesscommunications, and in particular to methods, apparatus and systems fortesting accuracy of Synchronization Signal Block (SSB) measurements in acellular communications network.

BACKGROUND

In a cellular communications network, a User Equipment (UE) can bemobile. The UE mobility can be verified using synchronization signals invarious cells of the network.

SUMMARY

In a general aspect, a UE in a cellular communications network receivesa first SSB corresponding to a first cell of the cellular communicationsnetwork, and a second SSB corresponding to a second cell of the cellularcommunications network. The UE clarifies a first Cell Identifier (ID) ofthe first cell. The UE clarifies a second cell ID of the second cell.The UE determines an SSB measurement accuracy value using the first cellID and the second cell ID.

Particular implementations may include one or more of the followingfeatures. In some implementations, clarifying the first cell ID of thefirst cell and the second cell ID of the second cell comprisesdetermining, by the UE, the first cell ID using one or more firstsignals received from a first base station corresponding to the firstcell; and determining, by the UE, the second cell ID using one or moresecond signals received from a second base station corresponding to thesecond cell. In some implementations, the one or more first signalsinclude one or more of a Primary Synchronization Signal (PSS) or aSecondary Synchronization Signal (SSS) received from the first basestation, and the one or more second signals include one or more of a PSSor an SSS received from the second base station. In someimplementations, the first base station includes one of an evolved NodeB(eNB) or a Next Generation NodeB (gNB), and the second base stationincludes one of an eNB or a gNB.

In some implementations, determining the SSB measurement accuracy valuecomprises: measuring a first Reference Signal Received Power (RSRP) forthe first cell; correlating the first RSRP to the first cell using thefirst cell ID; measuring a second RSRP for the second cell; correlatingthe second RSRP to the second cell using the second cell ID; adjustingthe first RSRP and the second RSRP in response to correlating the firstRSRP to the first cell and the second RSRP to the second cell; anddetermining the SSB measurement accuracy value using the adjusted firstRSRP and the second RSRP.

In some implementations, receiving the first SSB comprises receiving afirst New Radio Secondary Synchronization Signal (NR-SSS) correspondingto the first cell, and receiving the second SSB comprises receiving asecond NR-SSS corresponding to the second cell.

In some implementations, the UE determines whether to connect to thefirst cell or the second cell based on the SSB measurement accuracyvalue.

In another general aspect, a user equipment (UE) in a cellularcommunications network receives a first signal in a first SSB-basedMeasurement Timing Configuration (SMTC) window corresponding to a firstcell of the cellular communications network. The first signal isincluded in a first portion of the first SMTC window. The UE receives asecond signal in a second SMTC window corresponding to a second cell ofthe cellular communications network. The second signal is included in asecond portion of the second SMTC window, wherein the second portion ofthe second SMTC window does not overlap with the first portion of thefirst SMTC window. The UE determines a first Reference Signal ReceivedPower (RSRP) for the first cell using the first signal, and a secondRSRP for the second cell using the second signal.

Particular implementations may include one or more of the followingfeatures. In some implementations, receiving the first signal in thefirst SMTC window comprises receiving a New Radio SecondarySynchronization Signal (NR-SSS) in the first SMTC window. In someimplementations, receiving the second signal in the second SMTC windowcomprises receiving a NR-SSS in the second SMTC window.

In some implementations, receiving the first signal in the first SMTCwindow comprises obtaining a first Synchronization Signal Block (SSB)corresponding to the first cell from the first signal, and determiningthe first RSRP for the first cell comprises determining an SSB-basedRSRP for the first cell.

In some implementations, receiving the second signal in the second SMTCwindow comprises obtaining a second SSB corresponding to the second cellfrom the second signal, and determining the second RSRP for the secondcell comprises determining an SSB-based RSRP for the second cell.

In some implementations, determining the first RSRP and the second RSRPcomprises determining the first RSRP and the second RSRP independent ofone another. In some implementations, the first signal from the firstcell is time division multiplexed (TDM) with the second signal from thesecond cell. In some implementations, the UE determines whether toconnect to the first cell or the second cell based on the first RSRP andthe second RSRP.

In some implementations, receiving the first signal comprises receivingthe first signal from a first base station corresponding to the firstcell, and receiving the second signal comprises receiving the secondsignal from a second base station corresponding to the second cell. Insome implementations, the first base station includes one of an evolvedNodeB (eNB) or a Next Generation NodeB (gNB), and the second basestation includes one of an eNB or a gNB.

Similar operations and processes may be performed by one or morenon-transitory computer-readable media storing instructions that, whenexecuted by one or more processors, cause the one or more processors toperform the above-described operations and processes. Further, similaroperations may be performed by an apparatus or a system that includesone or more processors and one or more computer-readable media. The oneor more computer-readable media store instructions that, when executedby the one or more processors, cause the one or more processors toperform the above-described operations and processes. Additionally,similar operations can be associated with or provided ascomputer-implemented software embodied on tangible, non-transitory mediathat processes and transforms the respective data, some or all of theaspects may be computer-implemented methods or further included inrespective systems or other devices for performing this describedfunctionality.

The details of one or more disclosed implementations are set forth inthe accompanying drawings and the description below. Other features,aspects, and advantages will become apparent from the description, thedrawings and the claims.

BRIEF DESCRIPTION OF THE DRAWINGS

Figure A1 illustrates an example of SMTC windows for two cells with SSBsin separate portions of the respective SMTC windows.

FIG. 1 illustrates an example architecture of a communications networksystem, in accordance with various implementations.

FIG. 2 illustrates an example architecture of a system including a firstcore network, in accordance with various implementations.

FIG. 3 illustrates an example architecture of a system including asecond core network in accordance with various implementations.

FIG. 4 illustrates an example of infrastructure equipment in accordancewith various implementations.

FIG. 5 illustrates an example of a platform (or “device”) in accordancewith various implementations.

FIG. 6 illustrates example components of baseband circuitry and radiofront end modules (RFEM) in accordance with various implementations.

FIG. 7 illustrates protocol functions used in a wireless communicationdevice according to various implementations.

FIG. 8 illustrates components of a core network in accordance withvarious implementations.

FIG. 9 is a block diagram illustrating components of a system to supportNFV, according to some example implementations.

FIG. 10 is a block diagram illustrating components of electronic devicesable to read instructions from a machine-readable or computer-readablemedium (e.g., a non-transitory machine-readable storage medium) andperform any one or more of the methodologies discussed herein, accordingto some example implementations.

FIG. 11 illustrates a flowchart of a process for SSB measurementaccuracy testing.

FIG. 12 illustrates a flowchart of a second process for SSB measurementaccuracy testing.

Like reference numbers in the figures indicate like elements.

DETAILED DESCRIPTION

The following detailed description refers to the accompanying drawings.In the following description, for purposes of explanation and notlimitation, specific details are set forth such as particularstructures, architectures, interfaces, or techniques, among others, toprovide a thorough understanding of the various aspects of variousimplementations. However, it will be apparent to those skilled in theart having the benefit of the present disclosure that the variousaspects of the various implementations may be practiced in otherexamples that depart from these specific details. In certain instances,descriptions of well-known devices, circuits, and methods are omitted soas not to obscure the description of the various implementations withunnecessary detail. For the purposes of the present document, the phrase“A or B” means (A), (B), or (A and B).

This disclosure is generally directed to UE mobility in a cellularcommunications network. In the disclosed implementations, SSB basedmeasurement accuracy is tested to verify UE mobility. In someimplementations, for operations such as UE handover to a neighbor cell(for example, due to UE mobility), or adding a new CC in the case of CA,cell quality for neighbor cells is measured, using metrics such as theReference Signal Received Power (RSRP) or Reference Signal ReceivedQuality (RSRQ). This enables these processes to be performedappropriately, maintaining radio link quality. In 5G NR cellularnetworks, the cell quality is measured by using SS/PBCH Blocks (SSB),which include a Synchronization Signal (SS) and the Physical BroadcastCHannel (PBCH). The SSB periodicity can be configured for each cell, forexample, in the range of 5, 10, 20, 40, 80, or 160 milliseconds (ms).The disclosed implementations take into account variations in secondarysynchronization signal (SSS) correlation for different cell identity(cell ID) combinations in the cellular communications network.

For UE mobility, in some cases, two cells—a source (or serving) cell anda target (or neighbor) cell (referred to as cell 1 and cell 2respectively)—are considered for SSB based measurement accuracy test. Inconventional systems, SSS (for example, NR-SSS) are generated from thetwo cells simultaneously. When a UE moves from the source cell to thetarget cell and performs cell selection/reselection and handover, the UEmeasures the signal strength/quality of the neighbor cells. For example,the UE measures the target cell Reference Signal Received Power (RSRP)to decide whether it should connect to the new cell or not. The SSSgeneration is based on cell ID. The SSS correlation relationship canvary for different cell ID combinations, and the accuracy of RSRPmeasurements can vary for different cell ID combinations. In somescenarios, the RSRP accuracy can degrade more than 2 decibels (dB), suchthat the UE may not pass the test requirement, which can lead tomodifications in the accuracy requirement. It can be useful to provideadditional parameters for the measurement performance tests to improvethe accuracy of the results.

In the disclosed implementations, additional parameters are used withthe SSB measurement performance tests. In some implementations, cell IDsfor the source and target cells (cell 1 and cell 2) are clarified forthe tests. The SSB measurement value is determined upon clarifying thecell IDs for the source and target cells. In other implementations, theSSS (for example, NR-SSS) from cell 1 and cell 2 are time divisionmultiplexed (TDM) to mitigate the impact of signal interference. In suchimplementations, cell 1 and cell 2 transmit SSS in separate time slots,and the signal to interference and noise ratio (SINR) condition ischanged to signal to noise ratio (SNR) condition.

In some implementations, SSB-based Measurement Timing Configurationwindow (SMTC window) is used to notify UEs of the periodicity and timingof SSBs that the terminals can use for measurements. The SMTC windowperiodicity can be set in the same range as the SSB, for example, 5, 10,20, 40, 80, or 160 ms, and the duration of the window can be set to 1,2, 3, 4, or 5 ms, according to the number of SSBs transmitted on thecell being measured. When a UE has been notified of the SMTC window bythe base station, it detects and measures the SSBs within the SMTCwindow in a cell, and reports the measurement results back to the basestation. This can be the case, for example, in a 5G cellular network. Insome implementations, the number and position of SSB transmission in anSMTC window is different in different cells. For example, SSB in cell 1can transmitted in the first half of the corresponding SMTC window,while SSB in cell 2 can be transmitted in the second half of thecorresponding SMTC window, or vice versa. In such implementations, uponreceiving the SSB from cell 1 and cell 2 in respective SMTC windows, theUE calculates the SSB based RSRP of cell 1 and cell 2 independently.

Figure A1 illustrates an example of SMTC windows A102 and A112 for twocells with SSBs A104 and A114, respectively, in separate portions of therespective SMTC windows. As shown, the SMTC window A102 for the firstcell (for example, cell 1) includes the SSB A104 in a first portion ofthe SMTC window A102. In contrast, the SMTC window A112 for the secondcell (for example, cell 2) includes the SSB A114 in a second portion ofthe SMTC window A112, which does not overlap with the first portion ofthe SMTC window A102. Although Figure A1 shows the SMTC windows A102 andA112 as non-overlapping in time, in some implementations, the two SMTCwindows A102 and A112 overlap in time. In such implementations, SSB A104does not overlap with SSB A114, since the two SSBs are innon-overlapping portions of the respective windows.

The disclosed techniques are described in the following sectionsprimarily with respect to 5G New Radio (NR) networks. However, a personof ordinary skill in the art would readily understand that the disclosedtechniques are also applicable to other cellular networks, for example,cellular 3^(rd) Generation (3G) UMTS Terrestrial Radio Access (UMTS)networks, 4^(th) Generation (4G) Long Term Evolution (LTE) networks, or6^(th) Generation (6G) networks, among others.

FIG. 1 illustrates an example architecture of a communications networksystem 100, in accordance with various implementations. The followingdescription is provided for an example system 100 that operates inconjunction with cellular LTE system standards and/or 5G or NR systemstandards as provided by 3GPP technical specifications. However, theexample implementations are not limited in this regard and the describedimplementations may apply to other networks that benefit from theprinciples described herein, such as future 3GPP systems (for example,6G systems), IEEE 802.16 protocols (e.g., WMAN, WiMAX, etc.), or thelike.

As shown by FIG. 1 , the system 100 includes UE 101 a and UE 101 b(collectively referred to as “UEs 101” or “UE 101”). In someimplementations, one or more of the UEs 101 are configured to performthe SSB measurement tests that are described above.

In the illustrated example, UEs 101 are illustrated as smartphones(e.g., handheld touchscreen mobile computing devices connectable to oneor more cellular networks), but may also comprise any mobile ornon-mobile computing device, such as consumer electronics devices,cellular phones, smartphones, feature phones, tablet computers, wearablecomputer devices, personal digital assistants (PDAs), pagers, wirelesshandsets, desktop computers, laptop computers, in-vehicle infotainment(IVI), in-car entertainment (ICE) devices, an Instrument Cluster (IC),head-up display (HUD) devices, onboard diagnostic (OBD) devices, dashtopmobile equipment (DME), mobile data terminals (MDTs), Electronic EngineManagement System (EEMS), electronic/engine control units (ECUs),electronic/engine control modules (ECMs), embedded systems,microcontrollers, control modules, engine management systems (EMS),networked or “smart” appliances, machine type communications (MTC)devices, machine-to-machine (M2M), Internet of Things (IoT) devices,and/or the like.

In some implementations, any of the UEs 101 may be IoT UEs, which maycomprise a network access layer designed for low-power IoT applicationsutilizing short-lived UE connections. An IoT UE can utilize technologiessuch as M2M or MTC for exchanging data with an MTC server or device viaa PLMN, ProSe or D2D communication, sensor networks, or IoT networks.The M2M or MTC exchange of data may be a machine-initiated exchange ofdata. An IoT network describes interconnecting IoT UEs, which mayinclude uniquely identifiable embedded computing devices (within theInternet infrastructure), with short-lived connections. The IoT UEs mayexecute background applications (e.g., keep-alive messages, statusupdates, etc.) to facilitate the connections of the IoT network.

The UEs 101 may be configured to connect, for example, communicativelycouple, with a RAN 110. In implementations, the RAN 110 may be an NG RANor a 5G RAN, an E-UTRAN, or a legacy RAN, such as a UTRAN or GERAN. Asused herein, the term “NG RAN” or the like may refer to a RAN 110 thatoperates in an NR or 5G system 100, and the term “E-UTRAN” or the likemay refer to a RAN 110 that operates in an LTE or 4G system 100. The UEs101 utilize connections (or channels) 103 and 104, respectively, each ofwhich comprises a physical communications interface or layer (discussedin further detail below).

In this example, the connections 103 and 104 are illustrated as an airinterface to enable communicative coupling, and can be consistent withcellular communications protocols, such as a GSM protocol, a CDMAnetwork protocol, a PTT protocol, a POC protocol, a UMTS protocol, a3GPP LTE protocol, a 5G protocol, a NR protocol, and/or any of the othercommunications protocols discussed herein. In implementations, the UEs101 may directly exchange communication data via a ProSe interface 105.The ProSe interface 105 may alternatively be referred to as a SLinterface 105 and may comprise one or more logical channels, includingbut not limited to a PSCCH, a PSSCH, a PSDCH, and a PSBCH.

The UE 101 b is shown to be configured to access an access point AP 106(also referred to as “WLAN node 106,” “WLAN 106,” “WLAN Termination106,” “WT 106” or the like) via connection 107. The connection 107 cancomprise a local wireless connection, such as a connection consistentwith any IEEE 802.11 protocol, wherein the AP 106 would comprise awireless fidelity (Wi-Fi®) router. In this example, the AP 106 isconnected to the Internet without connecting to the core network of thewireless system (described in further detail below). In variousimplementations, the UE 101 b, RAN 110, and AP 106 may be configured toutilize LWA operation and/or LWIP operation. The LWA operation mayinvolve the UE 101 b in RRC_CONNECTED being configured by a RAN node 111a-b to utilize radio resources of LTE and WLAN. LWIP operation mayinvolve the UE 101 b using WLAN radio resources (e.g., connection 107)via IPsec protocol tunneling to authenticate and encrypt packets (e.g.,IP packets) sent over the connection 107. IPsec tunneling may includeencapsulating the entirety of original IP packets and adding a newpacket header, which protects the original header of the IP packets.

The RAN 110 can include one or more AN nodes or RAN nodes 111 a and 111b (collectively referred to as “RAN nodes 111” or “RAN node 111”) thatenable the connections 103 and 104. As used herein, the terms “accessnode,” “access point,” or the like may describe equipment that providesthe radio baseband functions for data and/or voice connectivity betweena network and one or more users. These access nodes can be referred toas BS, gNBs, RAN nodes, eNBs, NodeBs, RSUs, TRxPs or TRPs, and so forth,and can comprise ground stations (e.g., terrestrial access points) orsatellite stations providing coverage within a geographic area (e.g., acell). As used herein, the term “NG RAN node” or the like may refer to aRAN node 111 that operates in an NR or 5G system 100 (for example, agNB), and the term “E-UTRAN node” or the like may refer to a RAN node111 that operates in an LTE or 4G system 100 (e.g., an eNB). Accordingto various implementations, the RAN nodes 111 may be implemented as oneor more of a dedicated physical device such as a macrocell base station,and/or a low power (LP) base station for providing femtocells, picocellsor other like cells having smaller coverage areas, smaller usercapacity, or higher bandwidth compared to macrocells.

In some implementations, all or parts of the RAN nodes 111 may beimplemented as one or more software entities running on server computersas part of a virtual network, which may be referred to as a CRAN and/ora virtual baseband unit pool (vBBUP). In these implementations, the CRANor vBBUP may implement a RAN function split, such as a PDCP splitwherein RRC and PDCP layers are operated by the CRAN/vBBUP and other L2protocol entities are operated by individual RAN nodes 111; a MAC/PHYsplit wherein RRC, PDCP, RLC, and MAC layers are operated by theCRAN/vBBUP and the PHY layer is operated by individual RAN nodes 111; ora “lower PHY” split wherein RRC, PDCP, RLC, MAC layers and upperportions of the PHY layer are operated by the CRAN/vBBUP and lowerportions of the PHY layer are operated by individual RAN nodes 111. Thisvirtualized framework allows the freed-up processor cores of the RANnodes 111 to perform other virtualized applications. In someimplementations, an individual RAN node 111 may represent individualgNB-DUs that are connected to a gNB-CU via individual F1 interfaces (notshown by FIG. 1 ). In these implementations, the gNB-DUs may include oneor more remote radio heads or RFEMs (see, e.g., FIG. 4 ), and the gNB-CUmay be operated by a server that is located in the RAN 110 (not shown)or by a server pool in a similar manner as the CRAN/vBBUP. Additionallyor alternatively, one or more of the RAN nodes 111 may be nextgeneration eNBs (ng-eNBs), which are RAN nodes that provide E-UTRA userplane and control plane protocol terminations toward the UEs 101, andare connected to a 5GC (e.g., CN 320 of FIG. 3 ) via an NG interface(discussed infra).

In V2X scenarios one or more of the RAN nodes 111 may be or act as RoadSide Units (RSUs). The term “Road Side Unit” or “RSU” may refer to anytransportation infrastructure entity used for V2X communications. An RSUmay be implemented in or by a suitable RAN node or a stationary (orrelatively stationary) UE, where an RSU implemented in or by a UE may bereferred to as a “UE-type RSU,” an RSU implemented in or by an eNB maybe referred to as an “eNB-type RSU,” an RSU implemented in or by a gNBmay be referred to as a “gNB-type RSU,” and the like. In one example, anRSU is a computing device coupled with radio frequency circuitry locatedon a roadside that provides connectivity support to passing vehicle UEs101 (vUEs 101). The RSU may also include internal data storage circuitryto store intersection map geometry, traffic statistics, media, as wellas applications/software to sense and control ongoing vehicular andpedestrian traffic. The RSU may operate on the 5.9 GHz Direct ShortRange Communications (DSRC) band to provide very low latencycommunications for high speed events, such as crash avoidance, trafficwarnings, and the like. Additionally or alternatively, the RSU mayoperate on the cellular V2X band to provide the aforementioned lowlatency communications, as well as other cellular communicationsservices. Additionally or alternatively, the RSU may operate as a Wi-Fihotspot (2.4 GHz band) and/or provide connectivity to one or morecellular networks to provide uplink and downlink communications. Thecomputing device(s) and some or all of the radiofrequency circuitry ofthe RSU may be packaged in a weatherproof enclosure suitable for outdoorinstallation, and may include a network interface controller to providea wired connection (e.g., Ethernet) to a traffic signal controllerand/or a backhaul network.

Any of the RAN nodes 111 can terminate the air interface protocol andcan be the first point of contact for the UEs 101. In someimplementations, any of the RAN nodes 111 can fulfill various logicalfunctions for the RAN 110 including, but not limited to, radio networkcontroller (RNC) functions such as radio bearer management, uplink anddownlink dynamic radio resource management and data packet scheduling,and mobility management.

In implementations, the UEs 101 can be configured to communicate usingOFDM communication signals with each other or with any of the RAN nodes111 over a multicarrier communication channel in accordance with variouscommunication techniques, such as, but not limited to, an OFDMAcommunication technique (e.g., for downlink communications) or a SC-FDMAcommunication technique (e.g., for uplink and ProSe or sidelinkcommunications), although the scope of the implementations is notlimited in this respect. The OFDM signals can comprise a plurality oforthogonal subcarriers.

In some implementations, a downlink resource grid can be used fordownlink transmissions from any of the RAN nodes 111 to the UEs 101,while uplink transmissions can utilize similar techniques. The grid canbe a time-frequency grid, called a resource grid or time-frequencyresource grid, which is the physical resource in the downlink in eachslot. Such a time-frequency plane representation is a common practicefor OFDM systems, which makes it intuitive for radio resourceallocation. Each column and each row of the resource grid corresponds toone OFDM symbol and one OFDM subcarrier, respectively. The duration ofthe resource grid in the time domain corresponds to one slot in a radioframe. The smallest time-frequency unit in a resource grid is denoted asa resource element. Each resource grid comprises a number of resourceblocks, which describe the mapping of certain physical channels toresource elements. Each resource block comprises a collection ofresource elements; in the frequency domain, this may represent thesmallest quantity of resources that currently can be allocated. Thereare several different physical downlink channels that are conveyed usingsuch resource blocks.

According to various implementations, the UEs 101 and the RAN nodes 111communicate data (for example, transmit and receive) data over alicensed medium (also referred to as the “licensed spectrum” and/or the“licensed band”) and/or an unlicensed shared medium (also referred to asthe “unlicensed spectrum” and/or the “unlicensed band”). The licensedspectrum may include channels that operate in the frequency range ofapproximately 400 MHz to approximately 3.8 GHz, whereas the unlicensedspectrum may include the 5 GHz band.

To operate in the unlicensed spectrum, the UEs 101 and the RAN nodes 111may operate using LAA, eLAA, and/or feLAA mechanisms. In theseimplementations, the UEs 101 and the RAN nodes 111 may perform one ormore known medium-sensing operations and/or carrier-sensing operationsin order to determine whether one or more channels in the unlicensedspectrum is unavailable or otherwise occupied prior to transmitting inthe unlicensed spectrum. The medium/carrier sensing operations may beperformed according to a listen-before-talk (LBT) protocol.

LBT is a mechanism in which devices (for example, UEs 101 or RAN nodes111, etc.) senses a medium (for example, a channel or carrier frequency)and transmits when the medium is sensed to be idle (or when a specificchannel in the medium is sensed to be unoccupied). The medium sensingoperation may include CCA, which utilizes at least ED to determine thepresence or absence of other signals on a channel in order to determineif a channel is occupied or clear. This LBT mechanism allowscellular/LAA networks to coexist with incumbent systems in theunlicensed spectrum and with other LAA networks. ED may include sensingRF energy across an intended transmission band for a period of time andcomparing the sensed RF energy to a predefined or configured threshold.

Typically, the incumbent systems in the 5 GHz band are WLANs based onIEEE 802.11 technologies. WLAN employs a contention-based channel accessmechanism, called CSMA/CA. Here, when a WLAN node (e.g., a mobilestation (MS) such as UE 101, AP 106, or the like) intends to transmit,the WLAN node may first perform CCA before transmission. Additionally, abackoff mechanism is used to avoid collisions in situations where morethan one WLAN node senses the channel as idle and transmits at the sametime. The backoff mechanism may be a counter that is drawn randomlywithin the CWS, which is increased exponentially upon the occurrence ofcollision and reset to a minimum value when the transmission succeeds.The LBT mechanism designed for LAA is somewhat similar to the CSMA/CA ofWLAN. In some implementations, the LBT procedure for DL or ULtransmission bursts including PDSCH or PUSCH transmissions,respectively, may have an LAA contention window that is variable inlength between X and Y ECCA slots, where X and Y are minimum and maximumvalues for the CWSs for LAA. In one example, the minimum CWS for an LAAtransmission may be 9 microseconds (μs); however, the size of the CWSand a MCOT (for example, a transmission burst) may be based ongovernmental regulatory requirements.

The LAA mechanisms are built upon carrier aggregation (CA) technologiesof LTE-Advanced systems. In CA, each aggregated carrier is referred toas a component carrier (CC). A CC may have a bandwidth of 1.4, 3, 5, 10,15 or 20 MHz and a maximum of five CCs can be aggregated, resulting in amaximum aggregated bandwidth of 100 MHz. In FDD systems, the number ofaggregated carriers can be different for DL and UL, where the number ofUL CCs is equal to or lower than the number of DL component carriers. Insome cases, individual CCs can have a different bandwidth than otherCCs. In TDD systems, the number of CCs as well as the bandwidths of eachCC is usually the same for DL and UL.

CA also comprises individual serving cells to provide individual CCs.The coverage of the serving cells may differ, for example, because CCson different frequency bands will experience different pathloss. Aprimary service cell or PCell may provide a PCC for both UL and DL, andmay handle RRC and NAS related activities. The other serving cells arereferred to as SCells, and each SCell may provide an individual SCC forboth UL and DL. The SCCs may be added or removed as needed, whilechanging the PCC may require the UE 101 to undergo a handover. In LAA,eLAA, and feLAA, some or all of the SCells may operate in the unlicensedspectrum (referred to as “LAA SCells”), and the LAA SCells are assistedby a PCell operating in the licensed spectrum. When a UE is configuredwith more than one LAA SCell, the UE may receive UL grants on theconfigured LAA SCells indicating different PUSCH starting positionswithin a same subframe.

The PDSCH carries user data and higher-layer signaling to the UEs 101.The PDCCH carries information about the transport format and resourceallocations related to the PDSCH channel, among other things. It mayalso inform the UEs 101 about the transport format, resource allocation,and HARQ information related to the uplink shared channel. Typically,downlink scheduling (assigning control and shared channel resourceblocks to the UE 101 b within a cell) may be performed at any of the RANnodes 111 based on channel quality information fed back from any of theUEs 101. The downlink resource assignment information may be sent on thePDCCH used for (e.g., assigned to) each of the UEs 101.

The PDCCH uses CCEs to convey the control information. Before beingmapped to resource elements, the PDCCH complex-valued symbols may firstbe organized into quadruplets, which may then be permuted using asub-block interleaver for rate matching. Each PDCCH may be transmittedusing one or more of these CCEs, where each CCE may correspond to ninesets of four physical resource elements known as REGs. Four QuadraturePhase Shift Keying (QPSK) symbols may be mapped to each REG. The PDCCHcan be transmitted using one or more CCEs, depending on the size of theDCI and the channel condition. There can be four or more different PDCCHformats defined in LTE with different numbers of CCEs (e.g., aggregationlevel, L=1, 2, 4, or 8).

Some implementations may use concepts for resource allocation forcontrol channel information that are an extension of the above-describedconcepts. For example, some implementations may utilize an EPDCCH thatuses PDSCH resources for control information transmission. The EPDCCHmay be transmitted using one or more ECCEs. Similar to above, each ECCEmay correspond to nine sets of four physical resource elements known asan EREGs. An ECCE may have other numbers of EREGs in some situations.

The RAN nodes 111 may be configured to communicate with one another viainterface 112. In implementations where the system 100 is an LTE system(e.g., when CN 120 is an EPC 220 as in FIG. 2 ), the interface 112 maybe an X2 interface 112. The X2 interface may be defined between two ormore RAN nodes 111 (e.g., two or more eNBs and the like) that connect toEPC 120, and/or between two eNBs connecting to EPC 120. In someimplementations, the X2 interface may include an X2 user plane interface(X2-U) and an X2 control plane interface (X2-C). The X2-U may provideflow control mechanisms for user data packets transferred over the X2interface, and may be used to communicate information about the deliveryof user data between eNBs. For example, the X2-U may provide specificsequence number information for user data transferred from a MeNB to anSeNB; information about successful in sequence delivery of PDCP PDUs toa UE 101 from an SeNB for user data; information of PDCP PDUs that werenot delivered to a UE 101; information about a current minimum desiredbuffer size at the SeNB for transmitting to the UE user data; and thelike. The X2-C may provide intra-LTE access mobility functionality,including context transfers from source to target eNBs, user planetransport control, etc.; load management functionality; as well asinter-cell interference coordination functionality.

In implementations where the system 100 is a 5G or NR system (e.g., whenCN 120 is an 5GC 320 as in FIG. 3 ), the interface 112 may be an Xninterface 112. The Xn interface is defined between two or more RAN nodes111 (e.g., two or more gNBs and the like) that connect to 5GC 120,between a RAN node 111 (e.g., a gNB) connecting to 5GC 120 and an eNB,and/or between two eNBs connecting to 5GC 120. In some implementations,the Xn interface may include an Xn user plane (Xn-U) interface and an Xncontrol plane (Xn-C) interface. The Xn-U may provide non-guaranteeddelivery of user plane PDUs and support/provide data forwarding and flowcontrol functionality. The Xn-C may provide management and errorhandling functionality, functionality to manage the Xn-C interface;mobility support for UE 101 in a connected mode (e.g., CM-CONNECTED)including functionality to manage the UE mobility for connected modebetween one or more RAN nodes 111. The mobility support may includecontext transfer from an old (source) serving RAN node 111 to new(target) serving RAN node 111; and control of user plane tunnels betweenold (source) serving RAN node 111 to new (target) serving RAN node 111.A protocol stack of the Xn-U may include a transport network layer builton Internet Protocol (IP) transport layer, and a GTP-U layer on top of aUDP and/or IP layer(s) to carry user plane PDUs. The Xn-C protocol stackmay include an application layer signaling protocol (referred to as XnApplication Protocol (Xn-AP)) and a transport network layer that isbuilt on SCTP. The SCTP may be on top of an IP layer, and may providethe guaranteed delivery of application layer messages. In the transportIP layer, point-to-point transmission is used to deliver the signalingPDUs. In other implementations, the Xn-U protocol stack and/or the Xn-Cprotocol stack may be same or similar to the user plane and/or controlplane protocol stack(s) shown and described herein.

The RAN 110 is shown to be communicatively coupled to a core network—inthis implementation, core network (CN) 120. The CN 120 may comprise aplurality of network elements 122, which are configured to offer variousdata and telecommunications services to customers/subscribers (e.g.,users of UEs 101) who are connected to the CN 120 via the RAN 110. Thecomponents of the CN 120 may be implemented in one physical node orseparate physical nodes including components to read and executeinstructions from a machine-readable or computer-readable medium (e.g.,a non-transitory machine-readable storage medium). In someimplementations, NFV may be utilized to virtualize any or all of theabove-described network node functions via executable instructionsstored in one or more computer-readable storage mediums (described infurther detail below). A logical instantiation of the CN 120 may bereferred to as a network slice, and a logical instantiation of a portionof the CN 120 may be referred to as a network sub-slice. NFVarchitectures and infrastructures may be used to virtualize one or morenetwork functions, alternatively performed by proprietary hardware, ontophysical resources comprising a combination of industry-standard serverhardware, storage hardware, or switches. In other words, NFV systems canbe used to execute virtual or reconfigurable implementations of one ormore EPC components/functions.

Generally, the application server 130 may be an element offeringapplications that use IP bearer resources with the core network (e.g.,UMTS PS domain, LTE PS data services, etc.). The application server 130can also be configured to support one or more communication services(e.g., VoIP sessions, PTT sessions, group communication sessions, socialnetworking services, etc.) for the UEs 101 via the EPC 120.

In implementations, the CN 120 may be a 5GC (referred to as “5GC 120” orthe like), and the RAN 110 may be connected with the CN 120 via an NGinterface 113. In implementations, the NG interface 113 may be splitinto two parts, an NG user plane (NG-U) interface 114, which carriestraffic data between the RAN nodes 111 and a UPF, and the S1 controlplane (NG-C) interface 115, which is a signaling interface between theRAN nodes 111 and AMFs. Implementations where the CN 120 is a 5GC 120are discussed in more detail with regard to FIG. 3 .

In implementations, the CN 120 may be a 5G CN (referred to as “5GC 120”or the like), while in other implementations, the CN 120 may be an EPC).Where CN 120 is an EPC (referred to as “EPC 120” or the like), the RAN110 may be connected with the CN 120 via an S1 interface 113. Inimplementations, the S1 interface 113 may be split into two parts, an S1user plane (S1-U) interface 114, which carries traffic data between theRAN nodes 111 and the S-GW, and the S1-MME interface 115, which is asignaling interface between the RAN nodes 111 and MMEs.

FIG. 2 illustrates an example architecture of a system 200 including afirst core network (CN) 220, in accordance with various implementations.In this example, system 200 may implement the LTE standard wherein theCN 220 is an EPC 220 that corresponds to CN 120 of FIG. 1 .Additionally, the UE 201 may be the same or similar as the UEs 101 ofFIG. 1 , and the E-UTRAN 210 may be a RAN that is the same or similar tothe RAN 110 of FIG. 1 , and which may include RAN nodes 111 discussedpreviously. The CN 220 may comprise MMEs 221, an S-GW 222, a P-GW 223, aHSS 224, and a SGSN 225.

The MMEs 221 may be similar in function to the control plane of legacySGSN, and may implement MM functions to keep track of the currentlocation of a UE 201. The MMEs 221 may perform various MM procedures tomanage mobility aspects in access such as gateway selection and trackingarea list management. MM (also referred to as “EPS MM” or “EMM” inE-UTRAN systems) may refer to all applicable procedures, methods, datastorage, etc. that are used to maintain knowledge about a presentlocation of the UE 201, provide user identity confidentiality, and/orperform other like services to users/subscribers. Each UE 201 and theMME 221 may include an MM or EMM sublayer, and an MM context may beestablished in the UE 201 and the MME 221 when an attach procedure issuccessfully completed. The MM context may be a data structure ordatabase object that stores MM-related information of the UE 201. TheMMEs 221 may be coupled with the HSS 224 via an S6a reference point,coupled with the SGSN 225 via an S3 reference point, and coupled withthe S-GW 222 via an S11 reference point.

The SGSN 225 may be a node that serves the UE 201 by tracking thelocation of an individual UE 201 and performing security functions. Inaddition, the SGSN 225 may perform Inter-EPC node signaling for mobilitybetween 2G/3G and E-UTRAN 3GPP access networks; PDN and S-GW selectionas specified by the MMEs 221; handling of UE 201 time zone functions asspecified by the MMEs 221; and MME selection for handovers to E-UTRAN3GPP access network. The S3 reference point between the MMEs 221 and theSGSN 225 may enable user and bearer information exchange for inter-3GPPaccess network mobility in idle and/or active states.

The HSS 224 may comprise a database for network users, includingsubscription-related information to support the network entities'handling of communication sessions. The EPC 220 may comprise one orseveral HSSs 224, depending on the number of mobile subscribers, on thecapacity of the equipment, on the organization of the network, etc. Forexample, the HSS 224 can provide support for routing/roaming,authentication, authorization, naming/addressing resolution, locationdependencies, etc. An S6a reference point between the HSS 224 and theMMEs 221 may enable transfer of subscription and authentication data forauthenticating/authorizing user access to the EPC 220 between HSS 224and the MMEs 221.

The S-GW 222 may terminate the S1 interface 113 (“S1-U” in FIG. 2 )toward the RAN 210, and routes data packets between the RAN 210 and theEPC 220. In addition, the S-GW 222 may be a local mobility anchor pointfor inter-RAN node handovers and also may provide an anchor forinter-3GPP mobility. Other responsibilities may include lawfulintercept, charging, and some policy enforcement. The S11 referencepoint between the S-GW 222 and the MMEs 221 may provide a control planebetween the MMEs 221 and the S-GW 222. The S-GW 222 may be coupled withthe P-GW 223 via an S5 reference point.

The P-GW 223 may terminate an SGi interface toward a PDN 230. The P-GW223 may route data packets between the EPC 220 and external networkssuch as a network including the application server 130 (alternativelyreferred to as an “AF”) via an IP interface 125 (see e.g., FIG. 1 ). Inimplementations, the P-GW 223 may be communicatively coupled to anapplication server (application server 130 of FIG. 1 or PDN 230 in FIG.2 ) via an IP communications interface 125 (see, e.g., FIG. 1 ). The S5reference point between the P-GW 223 and the S-GW 222 may provide userplane tunneling and tunnel management between the P-GW 223 and the S-GW222. The S5 reference point may also be used for S-GW 222 relocation dueto UE 201 mobility and if the S-GW 222 needs to connect to anon-collocated P-GW 223 for the PDN connectivity. The P-GW 223 mayfurther include a node for policy enforcement and charging datacollection (e.g., PCEF (not shown)). Additionally, the SGi referencepoint between the P-GW 223 and the packet data network (PDN) 230 may bean operator external public, a private PDN, or an intra operator packetdata network, for example, for provision of IMS services. The P-GW 223may be coupled with a PCRF 226 via a Gx reference point.

PCRF 226 is the policy and charging control element of the EPC 220. In anon-roaming scenario, there may be a single PCRF 226 in the Home PublicLand Mobile Network (HPLMN) associated with a UE 201's Internet ProtocolConnectivity Access Network (IP-CAN) session. In a roaming scenario withlocal breakout of traffic, there may be two PCRFs associated with a UE201's IP-CAN session, a Home PCRF (H-PCRF) within an HPLMN and a VisitedPCRF (V-PCRF) within a Visited Public Land Mobile Network (VPLMN). ThePCRF 226 may be communicatively coupled to the application server 230via the P-GW 223. The application server 230 may signal the PCRF 226 toindicate a new service flow and select the appropriate QoS and chargingparameters. The PCRF 226 may provision this rule into a PCEF (not shown)with the appropriate TFT and QCI, which commences the QoS and chargingas specified by the application server 230. The Gx reference pointbetween the PCRF 226 and the P-GW 223 may allow for the transfer of QoSpolicy and charging rules from the PCRF 226 to PCEF in the P-GW 223. AnRx reference point may reside between the PDN 230 (or “AF 230”) and thePCRF 226.

FIG. 3 illustrates an architecture of an example system 300 including asecond core network (CN) 320 in accordance with various implementations.The system 300 is shown to include a UE 301, which may be the same orsimilar to the UEs 101 and UE 201 discussed previously; a (R)AN 310,which may be the same or similar to the RAN 110 and RAN 210 discussedpreviously, and which may include RAN nodes 111 discussed previously; aDN 303, which may be, for example, operator services, Internet access or3rd party services; and a CN 320, which is a 5GC in someimplementations. The 5GC 320 includes an AUSF 322; an AMF 321; a SMF324; a NEF 323; a PCF 326; a NRF 325; a UDM 327; an AF 328; a UPF 302;and a NSSF 329.

The UPF 302 may act as an anchor point for intra-RAT and inter-RATmobility, an external PDU session point of interconnect to DN 303, and abranching point to support multi-homed PDU session. The UPF 302 may alsoperform packet routing and forwarding, perform packet inspection,enforce the user plane part of policy rules, lawfully intercept packets(UP collection), perform traffic usage reporting, perform QoS handlingfor a user plane (e.g., packet filtering, gating, UL/DL rateenforcement), perform Uplink Traffic verification (e.g., SDF to QoS flowmapping), transport level packet marking in the uplink and downlink, andperform downlink packet buffering and downlink data notificationtriggering. UPF 302 may include an uplink classifier to support routingtraffic flows to a data network. The DN 303 may represent variousnetwork operator services, Internet access, or third party services. DN303 may include, or be similar to, application server 130 discussedpreviously. The UPF 302 may interact with the SMF 324 via an N4reference point between the SMF 324 and the UPF 302.

The AUSF 322 may store data for authentication of UE 301 and handleauthentication-related functionality. The AUSF 322 may facilitate acommon authentication framework for various access types. The AUSF 322may communicate with the AMF 321 via an N12 reference point between theAMF 321 and the AUSF 322; and may communicate with the UDM 327 via anN13 reference point between the UDM 327 and the AUSF 322. Additionally,the AUSF 322 may exhibit an Nausf service-based interface.

The AMF 321 may be responsible for registration management (e.g., forregistering UE 301, etc.), connection management, reachabilitymanagement, mobility management, and lawful interception of AMF-relatedevents, and access authentication and authorization. The AMF 321 may bea termination point for the an N11 reference point between the AMF 321and the SMF 324. The AMF 321 may provide transport for SM messagesbetween the UE 301 and the SMF 324, and act as a transparent proxy forrouting SM messages. AMF 321 may also provide transport for SMS messagesbetween UE 301 and an SMSF (not shown by FIG. 3 ). AMF 321 may act asSEAF, which may include interaction with the AUSF 322 and the UE 301,receipt of an intermediate key that was established as a result of theUE 301 authentication process. Where USIM based authentication is used,the AMF 321 may retrieve the security material from the AUSF 322. AMF321 may also include a SCM function, which receives a key from the SEAthat it uses to derive access-network specific keys. Furthermore, AMF321 may be a termination point of a RAN CP interface, which may includeor be an N2 reference point between the (R)AN 310 and the AMF 321; andthe AMF 321 may be a termination point of NAS (N1) signalling, andperform NAS ciphering and integrity protection.

AMF 321 may also support NAS signalling with a UE 301 over an N3 IWFinterface. The N3IWF may be used to provide access to untrustedentities. N3IWF may be a termination point for the N2 interface betweenthe (R)AN 310 and the AMF 321 for the control plane, and may be atermination point for the N3 reference point between the (R)AN 310 andthe UPF 302 for the user plane. As such, the AMF 321 may handle N2signalling from the SMF 324 and the AMF 321 for PDU sessions and QoS,encapsulate/de-encapsulate packets for IPSec and N3 tunnelling, mark N3user-plane packets in the uplink, and enforce QoS corresponding to N3packet marking taking into account QoS requirements associated with suchmarking received over N2. N3IWF may also relay uplink and downlinkcontrol-plane NAS signalling between the UE 301 and AMF 321 via an N1reference point between the UE 301 and the AMF 321, and relay uplink anddownlink user-plane packets between the UE 301 and UPF 302. The N3IWFalso provides mechanisms for IPsec tunnel establishment with the UE 301.The AMF 321 may exhibit an Namf service-based interface, and may be atermination point for an N14 reference point between two AMFs 321 and anN17 reference point between the AMF 321 and a 5G-EIR (not shown by FIG.3 ).

The UE 301 may need to register with the AMF 321 in order to receivenetwork services. RM is used to register or deregister the UE 301 withthe network (e.g., AMF 321), and establish a UE context in the network(e.g., AMF 321). The UE 301 may operate in an RM-REGISTERED state or anRM-DEREGISTERED state. In the RM-DEREGISTERED state, the UE 301 is notregistered with the network, and the UE context in AMF 321 holds novalid location or routing information for the UE 301 so the UE 301 isnot reachable by the AMF 321. In the RM-REGISTERED state, the UE 301 isregistered with the network, and the UE context in AMF 321 may hold avalid location or routing information for the UE 301 so the UE 301 isreachable by the AMF 321. In the RM-REGISTERED state, the UE 301 mayperform mobility Registration Update procedures, perform periodicRegistration Update procedures triggered by expiration of the periodicupdate timer (e.g., to notify the network that the UE 301 is stillactive), and perform a Registration Update procedure to update UEcapability information or to re-negotiate protocol parameters with thenetwork, among others.

The AMF 321 may store one or more RM contexts for the UE 301, where eachRM context is associated with a specific access to the network. The RMcontext may be a data structure, database object, etc. that indicates orstores, inter alia, a registration state per access type and theperiodic update timer. The AMF 321 may also store a 5GC MM context thatmay be the same or similar to the (E)MM context discussed previously. Invarious implementations, the AMF 321 may store a CE mode B Restrictionparameter of the UE 301 in an associated MM context or RM context. TheAMF 321 may also derive the value, when needed, from the UE's usagesetting parameter already stored in the UE context (and/or MM/RMcontext).

CM may be used to establish and release a signaling connection betweenthe UE 301 and the AMF 321 over the N1 interface. The signalingconnection is used to enable NAS signaling exchange between the UE 301and the CN 320, and comprises both the signaling connection between theUE and the AN (e.g., RRC connection or UE-N3IWF connection for non-3GPPaccess) and the N2 connection for the UE 301 between the AN (e.g., RAN310) and the AMF 321. The UE 301 may operate in one of two CM states,CM-IDLE mode or CM-CONNECTED mode. When the UE 301 is operating in theCM-IDLE state/mode, the UE 301 may have no NAS signaling connectionestablished with the AMF 321 over the N1 interface, and there may be(R)AN 310 signaling connection (e.g., N2 and/or N3 connections) for theUE 301. When the UE 301 is operating in the CM-CONNECTED state/mode, theUE 301 may have an established NAS signaling connection with the AMF 321over the N1 interface, and there may be a (R)AN 310 signaling connection(e.g., N2 and/or N3 connections) for the UE 301. Establishment of an N2connection between the (R)AN 310 and the AMF 321 may cause the UE 301 totransition from CM-IDLE mode to CM-CONNECTED mode, and the UE 301 maytransition from the CM-CONNECTED mode to the CM-IDLE mode when N2signaling between the (R)AN 310 and the AMF 321 is released.

The SMF 324 may be responsible for SM (e.g., session establishment,modify and release, including tunnel maintenance between UPF and ANnode); UE IP address allocation and management (including optionalauthorization); selection and control of UP function; configuringtraffic steering at UPF to route traffic to proper destination;termination of interfaces toward policy control functions; controllingpart of policy enforcement and QoS; lawful intercept (for SM events andinterface to LI system); termination of SM parts of NAS messages;downlink data notification; initiating AN specific SM information, sentvia AMF over N2 to AN; and determining SSC mode of a session. SM mayrefer to management of a PDU session, and a PDU session or “session” mayrefer to a PDU connectivity service that provides or enables theexchange of PDUs between a UE 301 and a data network (DN) 303 identifiedby a Data Network Name (DNN). PDU sessions may be established upon UE301 request, modified upon UE 301 and 5GC 320 request, and released uponUE 301 and 5GC 320 request using NAS SM signaling exchanged over the N1reference point between the UE 301 and the SMF 324. Upon request from anapplication server, the 5GC 320 may trigger a specific application inthe UE 301. In response to receipt of the trigger message, the UE 301may pass the trigger message (or relevant parts/information of thetrigger message) to one or more identified applications in the UE 301.The identified application(s) in the UE 301 may establish a PDU sessionto a specific DNN. The SMF 324 may check whether the UE 301 requests arecompliant with user subscription information associated with the UE 301.In this regard, the SMF 324 may retrieve and/or request to receiveupdate notifications on SMF 324 level subscription data from the UDM327.

The SMF 324 may include the following roaming functionality: handlinglocal enforcement to apply QoS SLAB (VPLMN); charging data collectionand charging interface (VPLMN); lawful intercept (in VPLMN for SM eventsand interface to LI system); and support for interaction with externalDN for transport of signalling for PDU sessionauthorization/authentication by external DN. An N16 reference pointbetween two SMFs 324 may be included in the system 300, which may bebetween another SMF 324 in a visited network and the SMF 324 in the homenetwork in roaming scenarios. Additionally, the SMF 324 may exhibit theNsmf service-based interface.

The NEF 323 may provide means for securely exposing the services andcapabilities provided by 3GPP network functions for third party,internal exposure/re-exposure, Application Functions (e.g., AF 328),edge computing or fog computing systems, etc. In such implementations,the NEF 323 may authenticate, authorize, and/or throttle the AFs. NEF323 may also translate information exchanged with the AF 328 andinformation exchanged with internal network functions. For example, theNEF 323 may translate between an AF-Service-Identifier and an internal5GC information. NEF 323 may also receive information from other networkfunctions (NFs) based on exposed capabilities of other networkfunctions. This information may be stored at the NEF 323 as structureddata, or at a data storage NF using standardized interfaces. The storedinformation can then be re-exposed by the NEF 323 to other NFs and AFs,and/or used for other purposes such as analytics. Additionally, the NEF323 may exhibit an Nnef service-based interface.

The NRF 325 may support service discovery functions, receive NFdiscovery requests from NF instances, and provide the information of thediscovered NF instances to the NF instances. NRF 325 also maintainsinformation of available NF instances and their supported services. Asused herein, the terms “instantiate,” “instantiation,” and the like mayrefer to the creation of an instance, and an “instance” may refer to aconcrete occurrence of an object, which may occur, for example, duringexecution of program code. Additionally, the NRF 325 may exhibit theNnrf service-based interface.

The PCF 326 may provide policy rules to control plane function(s) toenforce them, and may also support unified policy framework to governnetwork behaviour. The PCF 326 may also implement an FE to accesssubscription information relevant for policy decisions in a UDR of theUDM 327. The PCF 326 may communicate with the AMF 321 via an N15reference point between the PCF 326 and the AMF 321, which may include aPCF 326 in a visited network and the AMF 321 in case of roamingscenarios. The PCF 326 may communicate with the AF 328 via an N5reference point between the PCF 326 and the AF 328; and with the SMF 324via an N7 reference point between the PCF 326 and the SMF 324. Thesystem 300 and/or CN 320 may also include an N24 reference point betweenthe PCF 326 (in the home network) and a PCF 326 in a visited network.Additionally, the PCF 326 may exhibit an Npcf service-based interface.

The UDM 327 may handle subscription-related information to support thenetwork entities' handling of communication sessions, and may storesubscription data of UE 301. For example, subscription data may becommunicated between the UDM 327 and the AMF 321 via an N8 referencepoint between the UDM 327 and the AMF. The UDM 327 may include twoparts, an application FE and a UDR (the FE and UDR are not shown by FIG.3 ). The UDR may store subscription data and policy data for the UDM 327and the PCF 326, and/or structured data for exposure and applicationdata (including PFDs for application detection, application requestinformation for multiple UEs 301) for the NEF 323. The Nudrservice-based interface may be exhibited by the UDR 221 to allow the UDM327, PCF 326, and NEF 323 to access a particular set of the stored data,as well as to read, update (e.g., add, modify), delete, and subscribe tonotification of relevant data changes in the UDR. The UDM may include aUDM-FE, which is in charge of processing credentials, locationmanagement, subscription management and so on. Several different frontends may serve the same user in different transactions. The UDM-FEaccesses subscription information stored in the UDR and performsauthentication credential processing, user identification handling,access authorization, registration/mobility management, and subscriptionmanagement. The UDR may interact with the SMF 324 via an N10 referencepoint between the UDM 327 and the SMF 324. UDM 327 may also support SMSmanagement, wherein an SMS-FE implements the similar application logicas discussed previously. Additionally, the UDM 327 may exhibit the Nudmservice-based interface.

The AF 328 may provide application influence on traffic routing, provideaccess to the NCE, and interact with the policy framework for policycontrol. The NCE may be a mechanism that allows the 5GC 320 and AF 328to provide information to each other via NEF 323, which may be used foredge computing implementations. In such implementations, the networkoperator and third party services may be hosted close to the UE 301access point of attachment to achieve an efficient service deliverythrough the reduced end-to-end latency and load on the transportnetwork. For edge computing implementations, the 5GC may select a UPF302 close to the UE 301 and execute traffic steering from the UPF 302 toDN 303 via the N6 interface. This may be based on the UE subscriptiondata, UE location, and information provided by the AF 328. In this way,the AF 328 may influence UPF (re)selection and traffic routing. Based onoperator deployment, when AF 328 is considered to be a trusted entity,the network operator may permit AF 328 to interact directly withrelevant NFs. Additionally, the AF 328 may exhibit an Naf service-basedinterface.

The NSSF 329 may select a set of network slice instances serving the UE301. The NSSF 329 may also determine allowed NSSAI and the mapping tothe subscribed S-NSSAIs, if needed. The NSSF 329 may also determine theAMF set to be used to serve the UE 301, or a list of candidate AMF(s)321 based on a suitable configuration and possibly by querying the NRF325. The selection of a set of network slice instances for the UE 301may be triggered by the AMF 321 with which the UE 301 is registered byinteracting with the NSSF 329, which may lead to a change of AMF 321.The NSSF 329 may interact with the AMF 321 via an N22 reference pointbetween AMF 321 and NSSF 329; and may communicate with another NSSF 329in a visited network via an N31 reference point (not shown by FIG. 3 ).Additionally, the NSSF 329 may exhibit an Nnssf service-based interface.

As discussed previously, the CN 320 may include an SMSF, which may beresponsible for SMS subscription checking and verification, and relayingSM messages to/from the UE 301 to/from other entities, such as anSMS-GMSC/IWMSC/SMS-router. The SMS may also interact with AMF 321 andUDM 327 for a notification procedure that the UE 301 is available forSMS transfer (e.g., set a UE not reachable flag, and notifying UDM 327when UE 301 is available for SMS).

The CN 120 may also include other elements that are not shown by FIG. 3, such as a Data Storage system/architecture, a 5G-EIR, a SEPP, and thelike. The Data Storage system may include a SDSF, an UDSF, and/or thelike. Any NF may store and retrieve unstructured data into/from the UDSF(e.g., UE contexts), via N18 reference point between any NF and the UDSF(not shown by FIG. 3 ). Individual NFs may share a UDSF for storingtheir respective unstructured data or individual NFs may each have theirown UDSF located at or near the individual NFs. Additionally, the UDSFmay exhibit an Nudsf service-based interface (not shown by FIG. 3 ). The5G-EIR may be an NF that checks the status of PEI for determiningwhether particular equipment/entities are blacklisted from the network;and the SEPP may be a non-transparent proxy that performs topologyhiding, message filtering, and policing on inter-PLMN control planeinterfaces.

Additionally, there may be many more reference points and/orservice-based interfaces between the NF services in the NFs; however,these interfaces and reference points have been omitted from FIG. 3 forclarity. In one example, the CN 320 may include an Nx interface, whichis an inter-CN interface between the MME (e.g., MME 221) and the AMF 321in order to enable interworking between CN 320 and CN 220. Other exampleinterfaces/reference points may include an N5g-EIR service-basedinterface exhibited by a 5G-EIR, an N27 reference point between the NRFin the visited network and the NRF in the home network; and an N31reference point between the NSSF in the visited network and the NSSF inthe home network.

FIG. 4 illustrates an example of infrastructure equipment 400 inaccordance with various implementations. The infrastructure equipment400 (or “system 400”) may be implemented as a base station, radio head,RAN node such as the RAN nodes 111 and/or AP 106 shown and describedpreviously, application server(s) 130, and/or any other element/devicediscussed herein. In some cases, the system 400 may be implemented in orby a UE.

The system 400 includes application circuitry 405, baseband circuitry410, one or more radio front end modules (RFEMs) 415, memory circuitry420, power management integrated circuitry (PMIC) 425, power teecircuitry 430, network controller circuitry 435, network interfaceconnector 440, satellite positioning circuitry 445, and user interface450. In some implementations, the device 400 may include additionalelements such as, for example, memory/storage, display, camera, sensor,or input/output (I/O) interface. In other implementations, thecomponents described below may be included in more than one device. Forexample, said circuitries may be separately included in more than onedevice for CRAN, vBBU, or other like implementations.

Application circuitry 405 includes circuitry such as, but not limited toone or more processors (or processor cores), cache memory, and one ormore of low drop-out voltage regulators (LDOs), interrupt controllers,serial interfaces such as SPI, I²C or universal programmable serialinterface module, real time clock (RTC), timer-counters includinginterval and watchdog timers, general purpose input/output (I/O or M),memory card controllers such as Secure Digital (SD) MultiMediaCard (MMC)or similar, Universal Serial Bus (USB) interfaces, Mobile IndustryProcessor Interface (MIPI) interfaces and Joint Test Access Group (JTAG)test access ports. The processors (or cores) of the applicationcircuitry 405 may be coupled with or may include memory/storage elementsand may be configured to execute instructions stored in thememory/storage to enable various applications or operating systems torun on the system 400. In some implementations, the memory/storageelements may be on-chip memory circuitry, which may include any suitablevolatile and/or non-volatile memory, such as DRAM, SRAM, EPROM, EEPROM,Flash memory, solid-state memory, and/or any other type of memory devicetechnology, such as those discussed herein.

The processor(s) of application circuitry 405 may include, for example,one or more processor cores (CPUs), one or more application processors,one or more graphics processing units (GPUs), one or more reducedinstruction set computing (RISC) processors, one or more Acorn RISCMachine (ARM) processors, one or more complex instruction set computing(CISC) processors, one or more digital signal processors (DSP), one ormore FPGAs, one or more PLDs, one or more ASICs, one or moremicroprocessors or controllers, or any suitable combination thereof. Insome implementations, the application circuitry 405 may comprise, or maybe, a special-purpose processor/controller to operate according to thevarious implementations herein. As examples, the processor(s) ofapplication circuitry 405 may include one or more Intel Pentium®, Core®,or Xeon® processor(s); Advanced Micro Devices (AMD) Ryzen® processor(s),Accelerated Processing Units (APUs), or Epyc® processors; ARM-basedprocessor(s) licensed from ARM Holdings, Ltd. such as the ARM Cortex-Afamily of processors and the ThunderX2® provided by Cavium™, Inc.; aMIPS-based design from MIPS Technologies, Inc. such as MIPS WarriorP-class processors; and/or the like. In some implementations, the system400 may not utilize application circuitry 405, and instead may include aspecial-purpose processor/controller to process IP data received from anEPC or SGC, for example.

In some implementations, the application circuitry 405 may include oneor more hardware accelerators, which may be microprocessors,programmable processing devices, or the like. The one or more hardwareaccelerators may include, for example, computer vision (CV) and/or deeplearning (DL) accelerators. As examples, the programmable processingdevices may be one or more a field-programmable devices (FPDs) such asfield-programmable gate arrays (FPGAs) and the like; programmable logicdevices (PLDs) such as complex PLDs (CPLDs), high-capacity PLDs(HCPLDs), and the like; ASICs such as structured ASICs and the like;programmable SoCs (PSoCs); and the like. In such implementations, thecircuitry of application circuitry 405 may comprise logic blocks orlogic fabric, and other interconnected resources that may be programmedto perform various functions, such as the procedures, methods,functions, etc. of the various implementations discussed herein. In suchimplementations, the circuitry of application circuitry 405 may includememory cells (e.g., erasable programmable read-only memory (EPROM),electrically erasable programmable read-only memory (EEPROM), flashmemory, static memory (e.g., static random access memory (SRAM),anti-fuses, etc.)) used to store logic blocks, logic fabric, data, etc.in look-up-tables (LUTs) and the like.

The baseband circuitry 410 may be implemented, for example, as asolder-down substrate including one or more integrated circuits, asingle packaged integrated circuit soldered to a main circuit board or amulti-chip module that includes two or more integrated circuits. Thevarious hardware electronic elements of baseband circuitry 410 arediscussed infra with regard to FIG. 6 .

User interface circuitry 450 may include one or more user interfacesdesigned to enable user interaction with the system 400 or peripheralcomponent interfaces designed to enable peripheral component interactionwith the system 400. User interfaces may include, but are not limitedto, one or more physical or virtual buttons (e.g., a reset button), oneor more indicators (e.g., light emitting diodes (LEDs)), a physicalkeyboard or keypad, a mouse, a touchpad, a touchscreen, speakers orother audio emitting devices, microphones, a printer, a scanner, aheadset, a display screen or display device, etc. Peripheral componentinterfaces may include, but are not limited to, a nonvolatile memoryport, a universal serial bus (USB) port, an audio jack, a power supplyinterface, etc.

The radio front end modules (RFEMs) 415 may comprise a millimeter wave(mmWave) RFEM and one or more sub-mmWave radio frequency integratedcircuits (RFICs). In some implementations, the one or more sub-mmWaveRFICs may be physically separated from the mmWave RFEM. The RFICs mayinclude connections to one or more antennas or antenna arrays (see e.g.,antenna array 611 of FIG. 6 infra), and the RFEM may be connected tomultiple antennas. In alternative implementations, both mmWave andsub-mmWave radio functions may be implemented in the same physical RFEM415, which incorporates both mmWave antennas and sub-mmWave.

The memory circuitry 420 may include one or more of volatile memoryincluding dynamic random access memory (DRAM) and/or synchronous dynamicrandom access memory (SDRAM), and nonvolatile memory (NVM) includinghigh-speed electrically erasable memory (commonly referred to as Flashmemory), phase change random access memory (PRAM), magnetoresistiverandom access memory (MRAM), etc., and may incorporate thethree-dimensional (3D) cross-point (XPOINT) memories from Intel® andMicron®. Memory circuitry 420 may be implemented as one or more ofsolder down packaged integrated circuits, socketed memory modules andplug-in memory cards.

The PMIC 425 may include voltage regulators, surge protectors, poweralarm detection circuitry, and one or more backup power sources such asa battery or capacitor. The power alarm detection circuitry may detectone or more of brown out (under-voltage) and surge (over-voltage)conditions. The power tee circuitry 430 may provide for electrical powerdrawn from a network cable to provide both power supply and dataconnectivity to the infrastructure equipment 400 using a single cable.

The network controller circuitry 435 may provide connectivity to anetwork using a standard network interface protocol such as Ethernet,Ethernet over GRE Tunnels, Ethernet over Multiprotocol Label Switching(MPLS), or some other suitable protocol. Network connectivity may beprovided to/from the infrastructure equipment 400 via network interfaceconnector 440 using a physical connection, which may be electrical(commonly referred to as a “copper interconnect”), optical, or wireless.The network controller circuitry 435 may include one or more dedicatedprocessors and/or FPGAs to communicate using one or more of theaforementioned protocols. In some implementations, the networkcontroller circuitry 435 may include multiple controllers to provideconnectivity to other networks using the same or different protocols.

The positioning circuitry 445 includes circuitry to receive and decodesignals transmitted/broadcasted by a positioning network of a globalnavigation satellite system (GNSS). Examples of navigation satelliteconstellations (or GNSS) include United States' Global PositioningSystem (GPS), Russia's Global Navigation System (GLONASS), the EuropeanUnion's Galileo system, China's BeiDou Navigation Satellite System, aregional navigation system or GNSS augmentation system (e.g., Navigationwith Indian Constellation (NAVIC), Japan's Quasi-Zenith Satellite System(QZSS), France's Doppler Orbitography and Radio-positioning Integratedby Satellite (DORIS), etc.), or the like. The positioning circuitry 445comprises various hardware elements (e.g., including hardware devicessuch as switches, filters, amplifiers, antenna elements, and the like tofacilitate OTA communications) to communicate with components of apositioning network, such as navigation satellite constellation nodes.In some implementations, the positioning circuitry 445 may include aMicro-Technology for Positioning, Navigation, and Timing (Micro-PNT) ICthat uses a master timing clock to perform position tracking/estimationwithout GNSS assistance. The positioning circuitry 445 may also be partof, or interact with, the baseband circuitry 410 and/or RFEMs 415 tocommunicate with the nodes and components of the positioning network.The positioning circuitry 445 may also provide position data and/or timedata to the application circuitry 405, which may use the data tosynchronize operations with various infrastructure (e.g., RAN nodes 111,etc.), or the like.

The components shown by FIG. 4 may communicate with one another usinginterface circuitry, which may include any number of bus and/orinterconnect (IX) technologies such as industry standard architecture(ISA), extended ISA (EISA), peripheral component interconnect (PCI),peripheral component interconnect extended (PCIx), PCI express (PCIe),or any number of other technologies. The bus/IX may be a proprietarybus, for example, used in a SoC based system. Other bus/IX systems maybe included, such as an I²C interface, an SPI interface, point to pointinterfaces, and a power bus, among others.

FIG. 5 illustrates an example of a platform 500 (or “device 500”) inaccordance with various implementations. In implementations, theplatform 500 may be suitable for use as UEs 101, 201, 301, applicationservers 130, and/or any other element/device discussed herein. Theplatform 500 may include any combinations of the components shown in theexample. The components of platform 500 may be implemented as integratedcircuits (ICs), portions thereof, discrete electronic devices, or othermodules, logic, hardware, software, firmware, or a combination thereofadapted in the computer platform 500, or as components otherwiseincorporated within a chassis of a larger system. The block diagram ofFIG. 5 is intended to show a high level view of components of theplatform 500. However, some of the components shown may be omitted,additional components may be present, and different arrangement of thecomponents shown may occur in other implementations.

Application circuitry 505 includes circuitry such as, but not limitedto, one or more processors (or processor cores), cache memory, and oneor more of LDOs, interrupt controllers, serial interfaces such as SPI,I²C or universal programmable serial interface module, RTC,timer-counters including interval and watchdog timers, general purposeI/O, memory card controllers such as SD MMC or similar, USB interfaces,MIPI interfaces, and JTAG test access ports. The processors (or cores)of the application circuitry 505 may be coupled with or may includememory/storage elements and may be configured to execute instructionsstored in the memory/storage to enable various applications or operatingsystems to run on the system 500. In some implementations, thememory/storage elements may be on-chip memory circuitry, which mayinclude any suitable volatile and/or non-volatile memory, such as DRAM,SRAM, EPROM, EEPROM, Flash memory, solid-state memory, and/or any othertype of memory device technology, such as those discussed herein.

The processor(s) of application circuitry 405 may include, for example,one or more processor cores, one or more application processors, one ormore GPUs, one or more RISC processors, one or more ARM processors, oneor more CISC processors, one or more DSP, one or more FPGAs, one or morePLDs, one or more ASICs, one or more microprocessors or controllers, amultithreaded processor, an ultra-low voltage processor, an embeddedprocessor, some other known processing element, or any suitablecombination thereof. In some implementations, the application circuitry405 may comprise, or may be, a special-purpose processor/controller tooperate according to the various implementations herein.

As examples, the processor(s) of application circuitry 505 may includean Intel® Architecture Core™ based processor, such as a Quark™, anAtom™, an i3, an i5, an i7, or an MCU-class processor, or another suchprocessor available from Intel® Corporation, Santa Clara, Calif. Theprocessors of the application circuitry 505 may also be one or more ofAdvanced Micro Devices (AMD) Ryzen® processor(s) or AcceleratedProcessing Units (APUs); A5-A9 processor(s) from Apple® Inc.,Snapdragon™ processor(s) from Qualcomm® Technologies, Inc., TexasInstruments, Inc.® Open Multimedia Applications Platform (OMAP)™processor(s); a MIPS-based design from MIPS Technologies, Inc. such asMIPS Warrior M-class, Warrior I-class, and Warrior P-class processors;an ARM-based design licensed from ARM Holdings, Ltd., such as the ARMCortex-A, Cortex-R, and Cortex-M family of processors; or the like. Insome implementations, the application circuitry 505 may be a part of asystem on a chip (SoC) in which the application circuitry 505 and othercomponents are formed into a single integrated circuit, or a singlepackage, such as the Edison™ or Galileo™ SoC boards from Intel®Corporation.

Additionally or alternatively, application circuitry 505 may includecircuitry such as, but not limited to, one or more a field-programmabledevices (FPDs) such as FPGAs and the like; programmable logic devices(PLDs) such as complex PLDs (CPLDs), high-capacity PLDs (HCPLDs), andthe like; ASICs such as structured ASICs and the like; programmable SoCs(PSoCs); and the like. In such implementations, the circuitry ofapplication circuitry 505 may comprise logic blocks or logic fabric, andother interconnected resources that may be programmed to perform variousfunctions, such as the procedures, methods, functions, etc. of thevarious implementations discussed herein. In such implementations, thecircuitry of application circuitry 505 may include memory cells (e.g.,erasable programmable read-only memory (EPROM), electrically erasableprogrammable read-only memory (EEPROM), flash memory, static memory(e.g., static random access memory (SRAM), anti-fuses, etc.)) used tostore logic blocks, logic fabric, data, etc. in look-up tables (LUTs)and the like.

The baseband circuitry 510 may be implemented, for example, as asolder-down substrate including one or more integrated circuits, asingle packaged integrated circuit soldered to a main circuit board or amulti-chip module that includes two or more integrated circuits. Thevarious hardware electronic elements of baseband circuitry 510 arediscussed infra with regard to FIG. 6 .

The RFEMs 515 may comprise a millimeter wave (mmWave) RFEM and one ormore sub-mmWave radio frequency integrated circuits (RFICs). In someimplementations, the one or more sub-mmWave RFICs may be physicallyseparated from the mmWave RFEM. The RFICs may include connections to oneor more antennas or antenna arrays (see e.g., antenna array 611 of FIG.6 infra), and the RFEM may be connected to multiple antennas. Inalternative implementations, both mmWave and sub-mmWave radio functionsmay be implemented in the same physical RFEM 515, which incorporatesboth mmWave antennas and sub-mmWave.

The memory circuitry 520 may include any number and type of memorydevices used to provide for a given amount of system memory. Asexamples, the memory circuitry 520 may include one or more of volatilememory including random access memory (RAM), dynamic RAM (DRAM) and/orsynchronous dynamic RAM (SDRAM), and nonvolatile memory (NVM) includinghigh-speed electrically erasable memory (commonly referred to as Flashmemory), phase change random access memory (PRAM), magnetoresistiverandom access memory (MRAM), etc. The memory circuitry 520 may bedeveloped in accordance with a Joint Electron Devices EngineeringCouncil (JEDEC) low power double data rate (LPDDR)-based design, such asLPDDR2, LPDDR3, LPDDR4, or the like. Memory circuitry 520 may beimplemented as one or more of solder down packaged integrated circuits,single die package (SDP), dual die package (DDP) or quad die package(Q17P), socketed memory modules, dual inline memory modules (DIMMs)including microDIMMs or MiniDIMMs, and/or soldered onto a motherboardvia a ball grid array (BGA). In low power implementations, the memorycircuitry 520 may be on-die memory or registers associated with theapplication circuitry 505. To provide for persistent storage ofinformation such as data, applications, operating systems and so forth,memory circuitry 520 may include one or more mass storage devices, whichmay include, inter alia, a solid state disk drive (SSDD), hard diskdrive (HDD), a micro HDD, resistance change memories, phase changememories, holographic memories, or chemical memories, among others. Forexample, the computer platform 500 may incorporate the three-dimensional(3D) cross-point (XPOINT) memories from Intel® and Micron®.

Removable memory circuitry 523 may include devices, circuitry,enclosures/housings, ports or receptacles, etc. used to couple portabledata storage devices with the platform 500. These portable data storagedevices may be used for mass storage purposes, and may include, forexample, flash memory cards (e.g., Secure Digital (SD) cards, microSDcards, xD picture cards, and the like), and USB flash drives, opticaldiscs, external HDDs, and the like.

The platform 500 may also include interface circuitry (not shown) thatis used to connect external devices with the platform 500. The externaldevices connected to the platform 500 via the interface circuitryinclude sensor circuitry 521 and electro-mechanical components (EMCs)522, as well as removable memory devices coupled to removable memorycircuitry 523.

The sensor circuitry 521 include devices, modules, or subsystems whosepurpose is to detect events or changes in its environment and send theinformation (sensor data) about the detected events to some other adevice, module, subsystem, etc. Examples of such sensors include, interalia, inertia measurement units (IMUs) comprising accelerometers,gyroscopes, and/or magnetometers; microelectromechanical systems (MEMS)or nanoelectromechanical systems (NEMS) comprising 3-axisaccelerometers, 3-axis gyroscopes, and/or magnetometers; level sensors;flow sensors; temperature sensors (e.g., thermistors); pressure sensors;barometric pressure sensors; gravimeters; altimeters; image capturedevices (e.g., cameras or lensless apertures); light detection andranging (LiDAR) sensors; proximity sensors (e.g., infrared radiationdetector and the like), depth sensors, ambient light sensors, ultrasonictransceivers; microphones or other like audio capture devices; etc.

EMCs 522 include devices, modules, or subsystems whose purpose is toenable platform 500 to change its state, position, and/or orientation,or move or control a mechanism or (sub)system. Additionally, EMCs 522may be configured to generate and send messages/signalling to othercomponents of the platform 500 to indicate a current state of the EMCs522. Examples of the EMCs 522 include one or more power switches, relaysincluding electromechanical relays (EMRs) and/or solid state relays(SSRs), actuators (e.g., valve actuators, etc.), an audible soundgenerator, a visual warning device, motors (e.g., DC motors, steppermotors, etc.), wheels, thrusters, propellers, claws, clamps, hooks,and/or other like electro-mechanical components. In implementations.platform 500 is configured to operate one or more EMCs 522 based on oneor more captured events and/or instructions or control signals receivedfrom a service provider and/or various clients.

In some implementations, the interface circuitry may connect theplatform 500 with positioning circuitry 545. The positioning circuitry545 includes circuitry to receive and decode signalstransmitted/broadcasted by a positioning network of a GNSS. Examples ofnavigation satellite constellations (or GNSS) include United States'GPS, Russia's GLONASS, the European Union's Galileo system, China'sBeiDou Navigation Satellite System, a regional navigation system or GNSSaugmentation system (e.g., NAVIC), Japan's QZSS, France's DORIS, etc.),or the like. The positioning circuitry 545 comprises various hardwareelements (e.g., including hardware devices such as switches, filters,amplifiers, antenna elements, and the like to facilitate OTAcommunications) to communicate with components of a positioning network,such as navigation satellite constellation nodes. In someimplementations, the positioning circuitry 545 may include a Micro-PNTIC that uses a master timing clock to perform positiontracking/estimation without GNSS assistance. The positioning circuitry545 may also be part of, or interact with, the baseband circuitry 410and/or RFEMs 515 to communicate with the nodes and components of thepositioning network. The positioning circuitry 545 may also provideposition data and/or time data to the application circuitry 505, whichmay use the data to synchronize operations with various infrastructure(e.g., radio base stations), for turn-by-turn navigation applications,or the like

In some implementations, the interface circuitry may connect theplatform 500 with Near-Field Communication (NFC) circuitry 540. NFCcircuitry 540 is configured to provide contactless, short-rangecommunications based on radio frequency identification (RFID) standards,wherein magnetic field induction is used to enable communication betweenNFC circuitry 540 and NFC-enabled devices external to the platform 500(e.g., an “NFC touchpoint”). NFC circuitry 540 comprises an NFCcontroller coupled with an antenna element and a processor coupled withthe NFC controller. The NFC controller may be a chip/IC providing NFCfunctionalities to the NFC circuitry 540 by executing NFC controllerfirmware and an NFC stack. The NFC stack may be executed by theprocessor to control the NFC controller, and the NFC controller firmwaremay be executed by the NFC controller to control the antenna element toemit short-range RF signals. The RF signals may power a passive NFC tag(e.g., a microchip embedded in a sticker or wristband) to transmitstored data to the NFC circuitry 540, or initiate data transfer betweenthe NFC circuitry 540 and another active NFC device (e.g., a smartphoneor an NFC-enabled POS terminal) that is proximate to the platform 500.

The driver circuitry 546 may include software and hardware elements thatoperate to control particular devices that are embedded in the platform500, attached to the platform 500, or otherwise communicatively coupledwith the platform 500. The driver circuitry 546 may include individualdrivers allowing other components of the platform 500 to interact withor control various input/output (I/O) devices that may be presentwithin, or connected to, the platform 500. For example, driver circuitry546 may include a display driver to control and allow access to adisplay device, a touchscreen driver to control and allow access to atouchscreen interface of the platform 500, sensor drivers to obtainsensor readings of sensor circuitry 521 and control and allow access tosensor circuitry 521, EMC drivers to obtain actuator positions of theEMCs 522 and/or control and allow access to the EMCs 522, a cameradriver to control and allow access to an embedded image capture device,audio drivers to control and allow access to one or more audio devices.

The power management integrated circuitry (PMIC) 525 (also referred toas “power management circuitry 525”) may manage power provided tovarious components of the platform 500. In particular, with respect tothe baseband circuitry 510, the PMIC 525 may control power-sourceselection, voltage scaling, battery charging, or DC-to-DC conversion.The PMIC 525 may often be included when the platform 500 is capable ofbeing powered by a battery 530, for example, when the device is includedin a UE 101, 201, 301.

In some implementations, the PMIC 525 may control, or otherwise be partof, various power saving mechanisms of the platform 500. For example, ifthe platform 500 is in an RRC_Connected state, where it is stillconnected to the RAN node as it expects to receive traffic shortly, thenit may enter a state known as Discontinuous Reception Mode (DRX) after aperiod of inactivity. During this state, the platform 500 may power downfor brief intervals of time and thus save power. If there is no datatraffic activity for an extended period of time, then the platform 500may transition off to an RRC_Idle state, where it disconnects from thenetwork and does not perform operations such as channel qualityfeedback, handover, etc. The platform 500 goes into a very low powerstate and it performs paging where again it periodically wakes up tolisten to the network and then powers down again. The platform 500 maynot receive data in this state; in order to receive data, it transitionsback to RRC_Connected state. An additional power saving mode may allow adevice to be unavailable to the network for periods longer than a paginginterval (ranging from seconds to a few hours). During this time, thedevice is totally unreachable to the network and may power downcompletely. Any data sent during this time incurs a large delay and itis assumed the delay is acceptable.

A battery 530 may power the platform 500, although in some examples theplatform 500 may be mounted deployed in a fixed location, and may have apower supply coupled to an electrical grid. The battery 530 may be alithium ion battery, a metal-air battery, such as a zinc-air battery, analuminum-air battery, a lithium-air battery, and the like. In someimplementations, such as in V2X applications, the battery 530 may be atypical lead-acid automotive battery.

In some implementations, the battery 530 may be a “smart battery,” whichincludes or is coupled with a Battery Management System (BMS) or batterymonitoring integrated circuitry. The BMS may be included in the platform500 to track the state of charge (SoCh) of the battery 530. The BMS maybe used to monitor other parameters of the battery 530 to providefailure predictions, such as the state of health (SoH) and the state offunction (SoF) of the battery 530. The BMS may communicate theinformation of the battery 530 to the application circuitry 505 or othercomponents of the platform 500. The BMS may also include ananalog-to-digital (ADC) convertor that allows the application circuitry505 to directly monitor the voltage of the battery 530 or the currentflow from the battery 530. The battery parameters may be used todetermine actions that the platform 500 may perform, such astransmission frequency, network operation, sensing frequency, and thelike.

A power block, or other power supply coupled to an electrical grid maybe coupled with the BMS to charge the battery 530. In some examples, thepower block XS30 may be replaced with a wireless power receiver toobtain the power wirelessly, for example, through a loop antenna in thecomputer platform 500. In these examples, a wireless battery chargingcircuit may be included in the BMS. The specific charging circuitschosen may depend on the size of the battery 530, and thus, the requiredcurrent. The charging may be performed using the Airfuel standardpromulgated by the Airfuel Alliance, the Qi wireless charging standardpromulgated by the Wireless Power Consortium, or the Rezence chargingstandard promulgated by the Alliance for Wireless Power, among others.

User interface circuitry 550 includes various input/output (I/O) devicespresent within, or connected to, the platform 500, and includes one ormore user interfaces designed to enable user interaction with theplatform 500 and/or peripheral component interfaces designed to enableperipheral component interaction with the platform 500. The userinterface circuitry 550 includes input device circuitry and outputdevice circuitry. Input device circuitry includes any physical orvirtual means for accepting an input including, inter alia, one or morephysical or virtual buttons (e.g., a reset button), a physical keyboard,keypad, mouse, touchpad, touchscreen, microphones, scanner, headset,and/or the like. The output device circuitry includes any physical orvirtual means for showing information or otherwise conveyinginformation, such as sensor readings, actuator position(s), or otherlike information. Output device circuitry may include any number and/orcombinations of audio or visual display, including, inter alia, one ormore simple visual outputs/indicators (e.g., binary status indicators(e.g., light emitting diodes (LEDs)) and multi-character visual outputs,or more complex outputs such as display devices or touchscreens (e.g.,Liquid Chrystal Displays (LCD), LED displays, quantum dot displays,projectors, etc.), with the output of characters, graphics, multimediaobjects, and the like being generated or produced from the operation ofthe platform 500. The output device circuitry may also include speakersor other audio emitting devices, printer(s), and/or the like. In someimplementations, the sensor circuitry 521 may be used as the inputdevice circuitry (e.g., an image capture device, motion capture device,or the like) and one or more EMCs may be used as the output devicecircuitry (e.g., an actuator to provide haptic feedback or the like). Inanother example, NFC circuitry comprising an NFC controller coupled withan antenna element and a processing device may be included to readelectronic tags and/or connect with another NFC-enabled device.Peripheral component interfaces may include, but are not limited to, anon-volatile memory port, a USB port, an audio jack, a power supplyinterface, etc.

Although not shown, the components of platform 500 may communicate withone another using a suitable bus or interconnect (IX) technology, whichmay include any number of technologies, including ISA, EISA, PCI, PCIx,PCIe, a Time-Trigger Protocol (TTP) system, a FlexRay system, or anynumber of other technologies. The bus/IX may be a proprietary bus/IX,for example, used in a SoC based system. Other bus/IX systems may beincluded, such as an I²C interface, an SPI interface, point-to-pointinterfaces, and a power bus, among others.

FIG. 6 illustrates example components of baseband circuitry 610 andradio front end modules (RFEM) 615 in accordance with variousimplementations. The baseband circuitry 610 corresponds to the basebandcircuitry 410 and 510 of FIGS. 4 and 5 , respectively. The RFEM 615corresponds to the RFEM 415 and 515 of FIGS. 4 and 5 , respectively. Asshown, the RFEMs 615 may include Radio Frequency (RF) circuitry 606,front-end module (FEM) circuitry 608, antenna array 611 coupled togetherat least as shown.

The baseband circuitry 610 includes circuitry and/or control logicconfigured to carry out various radio/network protocol and radio controlfunctions that enable communication with one or more radio networks viathe RF circuitry 606. The radio control functions may include, but arenot limited to, signal modulation/demodulation, encoding/decoding, radiofrequency shifting, etc. In some implementations,modulation/demodulation circuitry of the baseband circuitry 610 mayinclude Fast-Fourier Transform (FFT), precoding, or constellationmapping/demapping functionality. In some implementations,encoding/decoding circuitry of the baseband circuitry 610 may includeconvolution, tail-biting convolution, turbo, Viterbi, or Low DensityParity Check (LDPC) encoder/decoder functionality. Implementations ofmodulation/demodulation and encoder/decoder functionality are notlimited to these examples and may include other suitable functionalityin other implementations. The baseband circuitry 610 is configured toprocess baseband signals received from a receive signal path of the RFcircuitry 606 and to generate baseband signals for a transmit signalpath of the RF circuitry 606. The baseband circuitry 610 is configuredto interface with application circuitry 405/505 (see FIGS. 4 and 5 ) forgeneration and processing of the baseband signals and for controllingoperations of the RF circuitry 606. The baseband circuitry 610 mayhandle various radio control functions.

The aforementioned circuitry and/or control logic of the basebandcircuitry 610 may include one or more single or multi-core processors.For example, the one or more processors may include a 3G basebandprocessor 604A, a 4G/LTE baseband processor 604B, a 5G/NR basebandprocessor 604C, or some other baseband processor(s) 604D for otherexisting generations, generations in development or to be developed inthe future (e.g., sixth generation (6G), etc.). In otherimplementations, some or all of the functionality of baseband processors604A-D may be included in modules stored in the memory 604G and executedvia a Central Processing Unit (CPU) 604E. In other implementations, someor all of the functionality of baseband processors 604A-D may beprovided as hardware accelerators (e.g., FPGAs, ASICs, etc.) loaded withthe appropriate bit streams or logic blocks stored in respective memorycells. In various implementations, the memory 604G may store programcode of a real-time OS (RTOS), which when executed by the CPU 604E (orother baseband processor), is to cause the CPU 604E (or other basebandprocessor) to manage resources of the baseband circuitry 610, scheduletasks, etc. Examples of the RTOS may include Operating System Embedded(OSE)™ provided by Enea®, Nucleus RTOS™ provided by Mentor Graphics®,Versatile Real-Time Executive (VRTX) provided by Mentor Graphics®,ThreadX™ provided by Express Logic®, FreeRTOS, REX OS provided byQualcomm®, OKL4 provided by Open Kernel (OK) Labs®, or any othersuitable RTOS, such as those discussed herein. In addition, the basebandcircuitry 610 includes one or more audio digital signal processor(s)(DSP) 604F. The audio DSP(s) 604F include elements forcompression/decompression and echo cancellation and may include othersuitable processing elements in other implementations.

In some implementations, each of the processors 604A-604E includerespective memory interfaces to send/receive data to/from the memory604G. The baseband circuitry 610 may further include one or moreinterfaces to communicatively couple to other circuitries/devices, suchas an interface to send/receive data to/from memory external to thebaseband circuitry 610; an application circuitry interface tosend/receive data to/from the application circuitry 405/505 of FIGS. 4-6); an RF circuitry interface to send/receive data to/from RF circuitry606 of FIG. 6 ; a wireless hardware connectivity interface tosend/receive data to/from one or more wireless hardware elements (e.g.,Near Field Communication (NFC) components, Bluetooth®/Bluetooth® LowEnergy components, Wi-Fi® components, and/or the like); and a powermanagement interface to send/receive power or control signals to/fromthe PMIC 525.

In alternate implementations (which may be combined with the abovedescribed implementations), baseband circuitry 610 comprises one or moredigital baseband systems, which are coupled with one another via aninterconnect subsystem and to a CPU subsystem, an audio subsystem, andan interface subsystem. The digital baseband subsystems may also becoupled to a digital baseband interface and a mixed-signal basebandsubsystem via another interconnect subsystem. Each of the interconnectsubsystems may include a bus system, point-to-point connections,network-on-chip (NOC) structures, and/or some other suitable bus orinterconnect technology, such as those discussed herein. The audiosubsystem may include DSP circuitry, buffer memory, program memory,speech processing accelerator circuitry, data converter circuitry suchas analog-to-digital and digital-to-analog converter circuitry, analogcircuitry including one or more of amplifiers and filters, and/or otherlike components. In an aspect of the present disclosure, basebandcircuitry 610 may include protocol processing circuitry with one or moreinstances of control circuitry (not shown) to provide control functionsfor the digital baseband circuitry and/or radio frequency circuitry(e.g., the radio front end modules 615).

Although not shown by FIG. 6 , in some implementations, the basebandcircuitry 610 includes individual processing device(s) to operate one ormore wireless communication protocols (e.g., a “multi-protocol basebandprocessor” or “protocol processing circuitry”) and individual processingdevice(s) to implement PHY layer functions. In these implementations,the PHY layer functions include the aforementioned radio controlfunctions. In these implementations, the protocol processing circuitryoperates or implements various protocol layers/entities of one or morewireless communication protocols. In a first example, the protocolprocessing circuitry may operate LTE protocol entities and/or 5G/NRprotocol entities when the baseband circuitry 610 and/or RF circuitry606 are part of mmWave communication circuitry or some other suitablecellular communication circuitry. In the first example, the protocolprocessing circuitry would operate MAC, RLC, PDCP, SDAP, RRC, and NASfunctions. In a second example, the protocol processing circuitry mayoperate one or more IEEE-based protocols when the baseband circuitry 610and/or RF circuitry 606 are part of a Wi-Fi communication system. In thesecond example, the protocol processing circuitry would operate Wi-FiMAC and logical link control (LLC) functions. The protocol processingcircuitry may include one or more memory structures (e.g., 604G) tostore program code and data for operating the protocol functions, aswell as one or more processing cores to execute the program code andperform various operations using the data. The baseband circuitry 610may also support radio communications for more than one wirelessprotocol.

The various hardware elements of the baseband circuitry 610 discussedherein may be implemented, for example, as a solder-down substrateincluding one or more integrated circuits (ICs), a single packaged ICsoldered to a main circuit board or a multi-chip module that includestwo or more ICs. In one example, the components of the basebandcircuitry 610 may be suitably combined in a single chip or chipset, ordisposed on a same circuit board. In another example, some or all of theconstituent components of the baseband circuitry 610 and RF circuitry606 may be implemented together such as, for example, a system on a chip(SoC) or System-in-Package (SiP). In another example, some or all of theconstituent components of the baseband circuitry 610 may be implementedas a separate SoC that is communicatively coupled with and RF circuitry606 (or multiple instances of RF circuitry 606). In yet another example,some or all of the constituent components of the baseband circuitry 610and the application circuitry 405/505 may be implemented together asindividual SoCs mounted to a same circuit board (e.g., a “multi-chippackage”).

In some implementations, the baseband circuitry 610 may provide forcommunication compatible with one or more radio technologies. Forexample, in some implementations, the baseband circuitry 610 may supportcommunication with an E-UTRAN or other WMAN, a WLAN, a WPAN.Implementations in which the baseband circuitry 610 is configured tosupport radio communications of more than one wireless protocol may bereferred to as multi-mode baseband circuitry.

RF circuitry 606 may enable communication with wireless networks usingmodulated electromagnetic radiation through a non-solid medium. Invarious implementations, the RF circuitry 606 may include switches,filters, amplifiers, etc. to facilitate the communication with thewireless network. RF circuitry 606 may include a receive signal path,which may include circuitry to down-convert RF signals received from theFEM circuitry 608 and provide baseband signals to the baseband circuitry610. RF circuitry 606 may also include a transmit signal path, which mayinclude circuitry to up-convert baseband signals provided by thebaseband circuitry 610 and provide RF output signals to the FEMcircuitry 608 for transmission.

In some implementations, the receive signal path of the RF circuitry 606may include mixer circuitry 606 a, amplifier circuitry 606 b and filtercircuitry 606 c. In some implementations, the transmit signal path ofthe RF circuitry 606 may include filter circuitry 606 c and mixercircuitry 606 a. RF circuitry 606 may also include synthesizer circuitry606 d for synthesizing a frequency for use by the mixer circuitry 606 aof the receive signal path and the transmit signal path. In someimplementations, the mixer circuitry 606 a of the receive signal pathmay be configured to down-convert RF signals received from the FEMcircuitry 608 based on the synthesized frequency provided by synthesizercircuitry 606 d. The amplifier circuitry 606 b may be configured toamplify the down-converted signals and the filter circuitry 606 c may bea low-pass filter (LPF) or band-pass filter (BPF) configured to removeunwanted signals from the down-converted signals to generate outputbaseband signals. Output baseband signals may be provided to thebaseband circuitry 610 for further processing. In some implementations,the output baseband signals may be zero-frequency baseband signals. Insome implementations, mixer circuitry 606 a of the receive signal pathmay comprise passive mixers, although the scope of the implementationsis not limited in this respect.

In some implementations, the mixer circuitry 606 a of the transmitsignal path may be configured to up-convert input baseband signals basedon the synthesized frequency provided by the synthesizer circuitry 606 dto generate RF output signals for the FEM circuitry 608. The basebandsignals may be provided by the baseband circuitry 610 and may befiltered by filter circuitry 606 c.

In some implementations, the mixer circuitry 606 a of the receive signalpath and the mixer circuitry 606 a of the transmit signal path mayinclude two or more mixers and may be arranged for quadraturedownconversion and upconversion, respectively. In some implementations,the mixer circuitry 606 a of the receive signal path and the mixercircuitry 606 a of the transmit signal path may include two or moremixers and may be arranged for image rejection (e.g., Hartley imagerejection). In some implementations, the mixer circuitry 606 a of thereceive signal path and the mixer circuitry 606 a of the transmit signalpath may be arranged for direct downconversion and direct upconversion,respectively. In some implementations, the mixer circuitry 606 a of thereceive signal path and the mixer circuitry 606 a of the transmit signalpath may be configured for super-heterodyne operation.

In some implementations, the output baseband signals and the inputbaseband signals may be analog baseband signals, although the scope ofthe implementations is not limited in this respect. In some alternateimplementations, the output baseband signals and the input basebandsignals may be digital baseband signals. In these alternateimplementations, the RF circuitry 606 may include analog-to-digitalconverter (ADC) and digital-to-analog converter (DAC) circuitry and thebaseband circuitry 610 may include a digital baseband interface tocommunicate with the RF circuitry 606.

In some dual-mode implementations, a separate radio IC circuitry may beprovided for processing signals for each spectrum, although the scope ofthe implementations is not limited in this respect.

In some implementations, the synthesizer circuitry 606 d may be afractional-N synthesizer or a fractional N/N+1 synthesizer, although thescope of the implementations is not limited in this respect as othertypes of frequency synthesizers may be suitable. For example,synthesizer circuitry 606 d may be a delta-sigma synthesizer, afrequency multiplier, or a synthesizer comprising a phase-locked loopwith a frequency divider.

The synthesizer circuitry 606 d may be configured to synthesize anoutput frequency for use by the mixer circuitry 606 a of the RFcircuitry 606 based on a frequency input and a divider control input. Insome implementations, the synthesizer circuitry 606 d may be afractional N/N+1 synthesizer.

In some implementations, frequency input is provided by a voltagecontrolled oscillator (VCO). Divider control input may be provided byeither the baseband circuitry 610 or the application circuitry 405/505depending on the desired output frequency. In some implementations, adivider control input (e.g., N) may be determined from a look-up tablebased on a channel indicated by the application circuitry 405/505.

Synthesizer circuitry 606 d of the RF circuitry 606 may include adivider, a delay-locked loop (DLL), a multiplexer and a phaseaccumulator. In some implementations, the divider may be a dual modulusdivider (DMD) and the phase accumulator may be a digital phaseaccumulator (DPA). In some implementations, the DMD may be configured todivide the input signal by either N or N+1 (e.g., based on a carry out)to provide a fractional division ratio. In some example implementations,the DLL may include a set of cascaded, tunable, delay elements, a phasedetector, a charge pump and a D-type flip-flop. In theseimplementations, the delay elements may be configured to break a VCOperiod up into Nd equal packets of phase, where Nd is the number ofdelay elements in the delay line. In this way, the DLL provides negativefeedback to help ensure that the total delay through the delay line isone VCO cycle.

In some implementations, synthesizer circuitry 606 d may be configuredto generate a carrier frequency as the output frequency, while in otherimplementations, the output frequency may be a multiple of the carrierfrequency (e.g., twice the carrier frequency, four times the carrierfrequency) and used in conjunction with quadrature generator and dividercircuitry to generate multiple signals at the carrier frequency withmultiple different phases with respect to each other. In someimplementations, the output frequency may be a LO frequency (fLO). Insome implementations, the RF circuitry 606 may include an IQ/polarconverter.

FEM circuitry 608 may include a receive signal path, which may includecircuitry configured to operate on RF signals received from antennaarray 611, amplify the received signals and provide the amplifiedversions of the received signals to the RF circuitry 606 for furtherprocessing. FEM circuitry 608 may also include a transmit signal path,which may include circuitry configured to amplify signals fortransmission provided by the RF circuitry 606 for transmission by one ormore of antenna elements of antenna array 611. In variousimplementations, the amplification through the transmit or receivesignal paths may be done solely in the RF circuitry 606, solely in theFEM circuitry 608, or in both the RF circuitry 606 and the FEM circuitry608.

In some implementations, the FEM circuitry 608 may include a TX/RXswitch to switch between transmit mode and receive mode operation. TheFEM circuitry 608 may include a receive signal path and a transmitsignal path. The receive signal path of the FEM circuitry 608 mayinclude an LNA to amplify received RF signals and provide the amplifiedreceived RF signals as an output (e.g., to the RF circuitry 606). Thetransmit signal path of the FEM circuitry 608 may include a poweramplifier (PA) to amplify input RF signals (e.g., provided by RFcircuitry 606), and one or more filters to generate RF signals forsubsequent transmission by one or more antenna elements of the antennaarray 611.

The antenna array 611 comprises one or more antenna elements, each ofwhich is configured convert electrical signals into radio waves totravel through the air and to convert received radio waves intoelectrical signals. For example, digital baseband signals provided bythe baseband circuitry 610 is converted into analog RF signals (e.g.,modulated waveform) that will be amplified and transmitted via theantenna elements of the antenna array 611 including one or more antennaelements (not shown). The antenna elements may be omnidirectional,direction, or a combination thereof. The antenna elements may be formedin a multitude of arranges as are known and/or discussed herein. Theantenna array 611 may comprise microstrip antennas or printed antennasthat are fabricated on the surface of one or more printed circuitboards. The antenna array 611 may be formed in as a patch of metal foil(e.g., a patch antenna) in a variety of shapes, and may be coupled withthe RF circuitry 606 and/or FEM circuitry 608 using metal transmissionlines or the like.

Processors of the application circuitry 405/505 and processors of thebaseband circuitry 610 may be used to execute elements of one or moreinstances of a protocol stack. For example, processors of the basebandcircuitry 610, alone or in combination, may be used execute Layer 3,Layer 2, or Layer 1 functionality, while processors of the applicationcircuitry 405/505 may utilize data (e.g., packet data) received fromthese layers and further execute Layer 4 functionality (e.g., TCP andUDP layers). As referred to herein, Layer 3 may comprise a RRC layer,described in further detail below. As referred to herein, Layer 2 maycomprise a MAC layer, an RLC layer, and a PDCP layer, described infurther detail below. As referred to herein, Layer 1 may comprise a PHYlayer of a UE/RAN node, described in further detail below.

FIG. 7 illustrates protocol functions used in a wireless communicationdevice according to various implementations. In particular, FIG. 7includes an arrangement 700 showing interconnections between variousprotocol layers/entities. The following description of FIG. 7 isprovided for various protocol layers/entities that operate inconjunction with the 5G/NR system standards and LTE system standards,but some or all of the aspects of FIG. 7 may be applicable to otherwireless communication network systems as well.

The protocol layers of arrangement 700 may include one or more of PHY710, MAC 720, RLC 730, PDCP 740, SDAP 747, RRC 755, and NAS layer 757,in addition to other higher layer functions not illustrated. Theprotocol layers may include one or more service access points (e.g.,items 759, 756, 750, 749, 745, 735, 725, and 715 in FIG. 7 ) that mayprovide communication between two or more protocol layers.

The PHY 710 may transmit and receive physical layer signals 705 that maybe received from or transmitted to one or more other communicationdevices. The physical layer signals 705 may comprise one or morephysical channels, such as those discussed herein. The PHY 710 mayfurther perform link adaptation or adaptive modulation and coding (AMC),power control, cell search (e.g., for initial synchronization andhandover purposes), and other measurements used by higher layers, suchas the RRC 755. The PHY 710 may still further perform error detection onthe transport channels, forward error correction (FEC) coding/decodingof the transport channels, modulation/demodulation of physical channels,interleaving, rate matching, mapping onto physical channels, and MIMOantenna processing. In implementations, an instance of PHY 710 mayprocess requests from and provide indications to an instance of MAC 720via one or more PHY-SAP 715. According to some implementations, requestsand indications communicated via PHY-SAP 715 may comprise one or moretransport channels.

Instance(s) of MAC 720 may process requests from, and provideindications to, an instance of RLC 730 via one or more MAC-SAPs 725.These requests and indications communicated via the MAC-SAP 725 maycomprise one or more logical channels. The MAC 720 may perform mappingbetween the logical channels and transport channels, multiplexing of MACSDUs from one or more logical channels onto TBs to be delivered to PHY710 via the transport channels, de-multiplexing MAC SDUs to one or morelogical channels from TBs delivered from the PHY 710 via transportchannels, multiplexing MAC SDUs onto TBs, scheduling informationreporting, error correction through HARQ, and logical channelprioritization.

Instance(s) of RLC 730 may process requests from and provide indicationsto an instance of PDCP 740 via one or more radio link control serviceaccess points (RLC-SAP) 735. These requests and indications communicatedvia RLC-SAP 735 may comprise one or more RLC channels. The RLC 730 mayoperate in a plurality of modes of operation, including: TransparentMode (TM), Unacknowledged Mode (UM), and Acknowledged Mode (AM). The RLC730 may execute transfer of upper layer protocol data units (PDUs),error correction through automatic repeat request (ARQ) for AM datatransfers, and concatenation, segmentation and reassembly of RLC SDUsfor UM and AM data transfers. The RLC 730 may also executere-segmentation of RLC data PDUs for AM data transfers, reorder RLC dataPDUs for UM and AM data transfers, detect duplicate data for UM and AMdata transfers, discard RLC SDUs for UM and AM data transfers, detectprotocol errors for AM data transfers, and perform RLC re-establishment.

Instance(s) of PDCP 740 may process requests from and provideindications to instance(s) of RRC 755 and/or instance(s) of SDAP 747 viaone or more packet data convergence protocol service access points(PDCP-SAP) 745. These requests and indications communicated via PDCP-SAP745 may comprise one or more radio bearers. The PDCP 740 may executeheader compression and decompression of IP data, maintain PDCP SequenceNumbers (SNs), perform in-sequence delivery of upper layer PDUs atre-establishment of lower layers, eliminate duplicates of lower layerSDUs at re-establishment of lower layers for radio bearers mapped on RLCAM, cipher and decipher control plane data, perform integrity protectionand integrity verification of control plane data, control timer-baseddiscard of data, and perform security operations (e.g., ciphering,deciphering, integrity protection, integrity verification, etc.).

Instance(s) of SDAP 747 may process requests from and provideindications to one or more higher layer protocol entities via one ormore SDAP-SAP 749. These requests and indications communicated viaSDAP-SAP 749 may comprise one or more QoS flows. The SDAP 747 may mapQoS flows to DRBs, and vice versa, and may also mark QFIs in DL and ULpackets. A single SDAP entity 747 may be configured for an individualPDU session. In the UL direction, the NG-RAN 110 may control the mappingof QoS Flows to DRB(s) in two different ways, reflective mapping orexplicit mapping. For reflective mapping, the SDAP 747 of a UE 101 maymonitor the QFIs of the DL packets for each DRB, and may apply the samemapping for packets flowing in the UL direction. For a DRB, the SDAP 747of the UE 101 may map the UL packets belonging to the QoS flows(s)corresponding to the QoS flow ID(s) and PDU session observed in the DLpackets for that DRB. To enable reflective mapping, the NG-RAN 310 maymark DL packets over the Uu interface with a QoS flow ID. The explicitmapping may involve the RRC 755 configuring the SDAP 747 with anexplicit QoS flow to DRB mapping rule, which may be stored and followedby the SDAP 747. In implementations, the SDAP 747 may only be used in NRimplementations and may not be used in LTE implementations.

The RRC 755 may configure, via one or more management service accesspoints (M-SAP), aspects of one or more protocol layers, which mayinclude one or more instances of PHY 710, MAC 720, RLC 730, PDCP 740 andSDAP 747. In implementations, an instance of RRC 755 may processrequests from and provide indications to one or more NAS entities 757via one or more RRC-SAPs 756. The main services and functions of the RRC755 may include broadcast of system information (e.g., included in MIBsor SIBs related to the NAS), broadcast of system information related tothe access stratum (AS), paging, establishment, maintenance and releaseof an RRC connection between the UE 101 and RAN 110 (e.g., RRCconnection paging, RRC connection establishment, RRC connectionmodification, and RRC connection release), establishment, configuration,maintenance and release of point to point Radio Bearers, securityfunctions including key management, inter-RAT mobility, and measurementconfiguration for UE measurement reporting. The MIBs and SIBs maycomprise one or more IEs, which may each comprise individual data fieldsor data structures.

The NAS 757 may form the highest stratum of the control plane betweenthe UE 101 and the AMF 321. The NAS 757 may support the mobility of theUEs 101 and the session management procedures to establish and maintainIP connectivity between the UE 101 and a P-GW in LTE systems.

According to various implementations, one or more protocol entities ofarrangement 700 may be implemented in UEs 101, RAN nodes 111, AMF 321 inNR implementations or MME 221 in LTE implementations, UPF 302 in NRimplementations or S-GW 222 and P-GW 223 in LTE implementations, or thelike to be used for control plane or user plane communications protocolstack between the aforementioned devices. In such implementations, oneor more protocol entities that may be implemented in one or more of UE101, gNB 111, AMF 321, etc. may communicate with a respective peerprotocol entity that may be implemented in or on another device usingthe services of respective lower layer protocol entities to perform suchcommunication. In some implementations, a gNB-CU of the gNB 111 may hostthe RRC 755, SDAP 747, and PDCP 740 of the gNB that controls theoperation of one or more gNB-DUs, and the gNB-DUs of the gNB 111 mayeach host the RLC 730, MAC 720, and PHY 710 of the gNB 111.

In a first example, a control plane protocol stack may comprise, inorder from highest layer to lowest layer, NAS 757, RRC 755, PDCP 740,RLC 730, MAC 720, and PHY 710. In this example, upper layers 760 may bebuilt on top of the NAS 757, which includes an IP layer 761, an SCTP762, and an application layer signaling protocol (AP) 763.

In NR implementations, the application protocol layer AP 763 may be anNG application protocol layer (NGAP or NG-AP) 763 for the NG interface113 defined between the NG-RAN node 111 and the AMF 321, or the AP 763may be an Xn application protocol layer (XnAP or Xn-AP) 763 for the Xninterface 112 that is defined between two or more RAN nodes 111.

The NG-AP 763 may support the functions of the NG interface 113 and maycomprise Elementary Procedures (EPs). An NG-AP EP may be a unit ofinteraction between the NG-RAN node 111 and the AMF 321. The NG-AP 763services may comprise two groups: UE-associated services (e.g., servicesrelated to a UE 101) and non-UE-associated services (e.g., servicesrelated to the whole NG interface instance between the NG-RAN node 111and AMF 321). These services may include functions including, but notlimited to: a paging function for the sending of paging requests toNG-RAN nodes 111 involved in a particular paging area; a UE contextmanagement function for allowing the AMF 321 to establish, modify,and/or release a UE context in the AMF 321 and the NG-RAN node 111; amobility function for UEs 101 in ECM-CONNECTED mode for intra-system HOsto support mobility within NG-RAN and inter-system HOs to supportmobility from/to EPS systems; a NAS Signaling Transport function fortransporting or rerouting NAS messages between UE 101 and AMF 321; a NASnode selection function for determining an association between the AMF321 and the UE 101; NG interface management function(s) for setting upthe NG interface and monitoring for errors over the NG interface; awarning message transmission function for providing means to transferwarning messages via NG interface or cancel ongoing broadcast of warningmessages; a Configuration Transfer function for requesting andtransferring of RAN configuration information (e.g., SON information,performance measurement (PM) data, etc.) between two RAN nodes 111 viaCN 120: and/or other like functions.

The XnAP 763 may support the functions of the Xn interface 112 and maycomprise XnAP basic mobility procedures and XnAP global procedures. TheXnAP basic mobility procedures may comprise procedures used to handle UEmobility within the NG RAN 111 (or E-UTRAN 210), such as handoverpreparation and cancellation procedures, SN Status Transfer procedures,UE context retrieval and UE context release procedures, RAN pagingprocedures, dual connectivity related procedures, and the like. The XnAPglobal procedures may comprise procedures that are not related to aspecific UE 101, such as Xn interface setup and reset procedures, NG-RANupdate procedures, cell activation procedures, and the like.

In LTE implementations, the AP 763 may be an S1 Application Protocollayer (S1-AP) 763 for the S1 interface 113 defined between an E-UTRANnode 111 and an MME, or the AP 763 may be an X2 application protocollayer (X2AP or X2-AP) 763 for the X2 interface 112 that is definedbetween two or more E-UTRAN nodes 111.

The S1 Application Protocol layer (S1-AP) 763 may support the functionsof the S1 interface, and similar to the NG-AP discussed previously, theS1-AP may comprise S1-AP EPs. An S1-AP EP may be a unit of interactionbetween the E-UTRAN node 111 and an MME 221 within an LTE CN 120. TheS1-AP 763 services may comprise two groups: UE-associated services andnon UE-associated services. These services perform functions including,but not limited to: E-UTRAN Radio Access Bearer (E-RAB) management, UEcapability indication, mobility, NAS signaling transport, RANInformation Management (RIM), and configuration transfer.

The X2AP 763 may support the functions of the X2 interface 112 and maycomprise X2AP basic mobility procedures and X2AP global procedures. TheX2AP basic mobility procedures may comprise procedures used to handle UEmobility within the E-UTRAN 120, such as handover preparation andcancellation procedures, SN Status Transfer procedures, UE contextretrieval and UE context release procedures, RAN paging procedures, dualconnectivity related procedures, and the like. The X2AP globalprocedures may comprise procedures that are not related to a specific UE101, such as X2 interface setup and reset procedures, load indicationprocedures, error indication procedures, cell activation procedures, andthe like.

The SCTP layer (alternatively referred to as the SCTP/IP layer) 762 mayprovide guaranteed delivery of application layer messages (e.g., NGAP orXnAP messages in NR implementations, or S1-AP or X2AP messages in LTEimplementations). The SCTP 762 may ensure reliable delivery of signalingmessages between the RAN node 111 and the AMF 321/MME 221 based, inpart, on the IP protocol, supported by the IP 761. The Internet Protocollayer (IP) 761 may be used to perform packet addressing and routingfunctionality. In some implementations the IP layer 761 may usepoint-to-point transmission to deliver and convey PDUs. In this regard,the RAN node 111 may comprise L2 and L1 layer communication links (e.g.,wired or wireless) with the MME/AMF to exchange information.

In a second example, a user plane protocol stack may comprise, in orderfrom highest layer to lowest layer, SDAP 747, PDCP 740, RLC 730, MAC720, and PHY 710. The user plane protocol stack may be used forcommunication between the UE 101, the RAN node 111, and UPF 302 in NRimplementations or an S-GW 222 and P-GW 223 in LTE implementations. Inthis example, upper layers 751 may be built on top of the SDAP 747, andmay include a user datagram protocol (UDP) and IP security layer(UDP/IP) 752, a General Packet Radio Service (GPRS) Tunneling Protocolfor the user plane layer (GTP-U) 753, and a User Plane PDU layer (UPPDU) 763.

The transport network layer 754 (also referred to as a “transportlayer”) may be built on IP transport, and the GTP-U 753 may be used ontop of the UDP/IP layer 752 (comprising a UDP layer and IP layer) tocarry user plane PDUs (UP-PDUs). The IP layer (also referred to as the“Internet layer”) may be used to perform packet addressing and routingfunctionality. The IP layer may assign IP addresses to user data packetsin any of IPv4, IPv6, or PPP formats, for example.

The GTP-U 753 may be used for carrying user data within the GPRS corenetwork and between the radio access network and the core network. Theuser data transported can be packets in any of IPv4, IPv6, or PPPformats, for example. The UDP/IP 752 may provide checksums for dataintegrity, port numbers for addressing different functions at the sourceand destination, and encryption and authentication on the selected dataflows. The RAN node 111 and the S-GW 222 may utilize an S1-U interfaceto exchange user plane data via a protocol stack comprising an L1 layer(e.g., PHY 710), an L2 layer (e.g., MAC 720, RLC 730, PDCP 740, and/orSDAP 747), the UDP/IP layer 752, and the GTP-U 753. The S-GW 222 and theP-GW 223 may utilize an S5/S8 a interface to exchange user plane datavia a protocol stack comprising an L1 layer, an L2 layer, the UDP/IPlayer 752, and the GTP-U 753. As discussed previously, NAS protocols maysupport the mobility of the UE 101 and the session management proceduresto establish and maintain IP connectivity between the UE 101 and theP-GW 223.

Moreover, although not shown by FIG. 7 , an application layer may bepresent above the AP 763 and/or the transport network layer 754. Theapplication layer may be a layer in which a user of the UE 101, RAN node111, or other network element interacts with software applications beingexecuted, for example, by application circuitry 405 or applicationcircuitry 505, respectively. The application layer may also provide oneor more interfaces for software applications to interact withcommunications systems of the UE 101 or RAN node 111, such as thebaseband circuitry 610. In some implementations the IP layer and/or theapplication layer may provide the same or similar functionality aslayers 5-7, or portions thereof, of the Open Systems Interconnection(OSI) model (e.g., OSI Layer 7—the application layer, OSI Layer 6—thepresentation layer, and OSI Layer 5—the session layer).

FIG. 8 illustrates components of a core network 220 in accordance withvarious implementations. The components of the core network (CN) 220 maybe implemented in one physical node or separate physical nodes includingcomponents to read and execute instructions from a machine-readable orcomputer-readable medium (e.g., a non-transitory machine-readablestorage medium). In implementations, the components of CN 320 may beimplemented in a same or similar manner as discussed herein with regardto the components of CN 220. In some implementations, NFV is utilized tovirtualize any or all of the above-described network node functions viaexecutable instructions stored in one or more computer-readable storagemediums (described in further detail below). A logical instantiation ofthe CN 220 may be referred to as a network slice 801, and individuallogical instantiations of the CN 220 may provide specific networkcapabilities and network characteristics. A logical instantiation of aportion of the CN 220 may be referred to as a network sub-slice 802(e.g., the network sub-slice 802 is shown to include the P-GW 223 andthe PCRF 226).

As used herein, the terms “instantiate,” “instantiation,” and the likemay refer to the creation of an instance, and an “instance” may refer toa concrete occurrence of an object, which may occur, for example, duringexecution of program code. A network instance may refer to informationidentifying a domain, which may be used for traffic detection androuting in case of different IP domains or overlapping IP addresses. Anetwork slice instance may refer to a set of network functions (NFs)instances and the resources (e.g., compute, storage, and networkingresources) used to deploy the network slice.

With respect to 5G systems (see, e.g., FIG. 3 ), a network slice alwayscomprises a RAN part and a CN part. The support of network slicingrelies on the principle that traffic for different slices is handled bydifferent PDU sessions. The network can realize the different networkslices by scheduling and also by providing different L1/L2configurations. The UE 301 provides assistance information for networkslice selection in an appropriate RRC message, if it has been providedby NAS. While the network can support large number of slices, the UEneed not support more than 8 slices simultaneously.

A network slice may include the CN 320 control plane and user plane NFs,NG-RANs 310 in a serving PLMN, and a N3IWF functions in the servingPLMN. Individual network slices may have different S-NSSAI and/or mayhave different SSTs. NSSAI includes one or more S-NSSAIs, and eachnetwork slice is uniquely identified by an S-NSSAI. Network slices maydiffer for supported features and network functions optimizations,and/or multiple network slice instances may deliver the sameservice/features but for different groups of UEs 301 (e.g., enterpriseusers). For example, individual network slices may deliver differentcommitted service(s) and/or may be dedicated to a particular customer orenterprise. In this example, each network slice may have differentS-NSSAIs with the same SST but with different slice differentiators.Additionally, a single UE may be served with one or more network sliceinstances simultaneously via a 5G AN and associated with eight differentS-NSSAIs. Moreover, an AMF 321 instance serving an individual UE 301 maybelong to each of the network slice instances serving that UE.

Network Slicing in the NG-RAN 310 involves RAN slice awareness. RANslice awareness includes differentiated handling of traffic fordifferent network slices, which have been pre-configured. Sliceawareness in the NG-RAN 310 is introduced at the PDU session level byindicating the S-NSSAI corresponding to a PDU session in all signalingthat includes PDU session resource information. How the NG-RAN 310supports the slice enabling in terms of NG-RAN functions (e.g., the setof network functions that comprise each slice) is implementationdependent. The NG-RAN 310 selects the RAN part of the network sliceusing assistance information provided by the UE 301 or the 5GC 320,which unambiguously identifies one or more of the pre-configured networkslices in the PLMN. The NG-RAN 310 also supports resource management andpolicy enforcement between slices as per SLAs. A single NG-RAN node maysupport multiple slices, and the NG-RAN 310 may also apply anappropriate RRM policy for the SLA in place to each supported slice. TheNG-RAN 310 may also support QoS differentiation within a slice.

The NG-RAN 310 may also use the UE assistance information for theselection of an AMF 321 during an initial attach, if available. TheNG-RAN 310 uses the assistance information for routing the initial NASto an AMF 321. If the NG-RAN 310 is unable to select an AMF 321 usingthe assistance information, or the UE 301 does not provide any suchinformation, the NG-RAN 310 sends the NAS signaling to a default AMF321, which may be among a pool of AMFs 32L For subsequent accesses, theUE 301 provides a temp ID, which is assigned to the UE 301 by the 5GC320, to enable the NG-RAN 310 to route the NAS message to theappropriate AMF 321 as long as the temp ID is valid. The NG-RAN 310 isaware of, and can reach, the AMF 321 that is associated with the tempID. Otherwise, the method for initial attach applies.

The NG-RAN 310 supports resource isolation between slices. NG-RAN 310resource isolation may be achieved by means of RRM policies andprotection mechanisms that should avoid that shortage of sharedresources if one slice breaks the service level agreement for anotherslice. In some implementations, it is possible to fully dedicate NG-RAN310 resources to a certain slice. How NG-RAN 310 supports resourceisolation is implementation dependent.

Some slices may be available only in part of the network. Awareness inthe NG-RAN 310 of the slices supported in the cells of its neighbors maybe beneficial for inter-frequency mobility in connected mode. The sliceavailability may not change within the UE's registration area. TheNG-RAN 310 and the 5GC 320 are responsible to handle a service requestfor a slice that may or may not be available in a given area. Admissionor rejection of access to a slice may depend on factors such as supportfor the slice, availability of resources, support of the requestedservice by NG-RAN 310.

The UE 301 may be associated with multiple network slicessimultaneously. In case the UE 301 is associated with multiple slicessimultaneously, only one signaling connection is maintained, and forintra-frequency cell reselection, the UE 301 tries to camp on the bestcell. For inter-frequency cell reselection, dedicated priorities can beused to control the frequency on which the UE 301 camps. The 5GC 320 isto validate that the UE 301 has the rights to access a network slice.Prior to receiving an Initial Context Setup Request message, the NG-RAN310 may be allowed to apply some provisional/local policies, based onawareness of a particular slice that the UE 301 is requesting to access.During the initial context setup, the NG-RAN 310 is informed of theslice for which resources are being requested.

NFV architectures and infrastructures may be used to virtualize one ormore NFs, alternatively performed by proprietary hardware, onto physicalresources comprising a combination of industry-standard server hardware,storage hardware, or switches. In other words, NFV systems can be usedto execute virtual or reconfigurable implementations of one or more EPCcomponents/functions.

FIG. 9 is a block diagram illustrating components of a system 900 tosupport NFV, according to some example implementations. The system 900is illustrated as including a VIM 902, an NFVI 904, an VNFM 906, VNFs908, an EM 910, an NFVO 912, and a NM 914.

The VIM 902 manages the resources of the NFVI 904. The NFVI 904 caninclude physical or virtual resources and applications (includinghypervisors) used to execute the system 900. The VIM 902 may manage thelife cycle of virtual resources with the NFVI 904 (e.g., creation,maintenance, and tear down of VMs associated with one or more physicalresources), track VM instances, track performance, fault and security ofVM instances and associated physical resources, and expose VM instancesand associated physical resources to other management systems.

The VNFM 906 may manage the VNFs 908. The VNFs 908 may be used toexecute EPC components/functions. The VNFM 906 may manage the life cycleof the VNFs 908 and track performance, fault and security of the virtualaspects of VNFs 908. The EM 910 may track the performance, fault andsecurity of the functional aspects of VNFs 908. The tracking data fromthe VNFM 906 and the EM 910 may comprise, for example, PM data used bythe VIM 902 or the NFVI 904. Both the VNFM 906 and the EM 910 can scaleup/down the quantity of VNFs of the system 900.

The NFVO 912 may coordinate, authorize, release and engage resources ofthe NFVI 904 in order to provide the requested service (e.g., to executean EPC function, component, or slice). The NM 914 may provide a packageof end-user functions with the responsibility for the management of anetwork, which may include network elements with VNFs, non-virtualizednetwork functions, or both (management of the VNFs may occur via the EM910).

FIG. 10 is a block diagram illustrating components of electronic devicesable to read instructions from a machine-readable or computer-readablemedium (e.g., a non-transitory machine-readable storage medium) andperform any one or more of the methodologies discussed herein, accordingto some example implementations. Specifically, FIG. 10 shows adiagrammatic representation of hardware resources 1000 including one ormore processors (or processor cores) 1010, one or more memory/storagedevices 1020, and one or more communication resources 1030, each ofwhich may be communicatively coupled via a bus 1040. For implementationswhere node virtualization (e.g., NFV) is utilized, a hypervisor 1002 maybe executed to provide an execution environment for one or more networkslices/sub-slices to utilize the hardware resources 1000.

The processors 1010 may include, for example, a processor 1012 and aprocessor 1014. The processor(s) 1010 may be, for example, a centralprocessing unit (CPU), a reduced instruction set computing (RISC)processor, a complex instruction set computing (CISC) processor, agraphics processing unit (GPU), a DSP such as a baseband processor, anASIC, an FPGA, a radio-frequency integrated circuit (RFIC), anotherprocessor (including those discussed herein), or any suitablecombination thereof

The memory/storage devices 1020 may include main memory, disk storage,or any suitable combination thereof. The memory/storage devices 1020 mayinclude, but are not limited to, any type of volatile or nonvolatilememory such as dynamic random access memory (DRAM), static random accessmemory (SRAM), erasable programmable read-only memory (EPROM),electrically erasable programmable read-only memory (EEPROM), Flashmemory, solid-state storage, etc.

The communication resources 1030 may include interconnection or networkinterface components or other suitable devices to communicate with oneor more peripheral devices 1004 or one or more databases 1006 via anetwork 1008. For example, the communication resources 1030 may includewired communication components (e.g., for coupling via USB), cellularcommunication components, NFC components, Bluetooth® (or Bluetooth® LowEnergy) components, Wi-Fi® components, and other communicationcomponents.

Instructions 1050 may comprise software, a program, an application, anapplet, an app, or other executable code for causing at least any of theprocessors 1010 to perform any one or more of the methodologiesdiscussed herein. The instructions 1050 may reside, completely orpartially, within at least one of the processors 1010 (e.g., within theprocessor's cache memory), the memory/storage devices 1020, or anysuitable combination thereof. Furthermore, any portion of theinstructions 1050 may be transferred to the hardware resources 1000 fromany combination of the peripheral devices 1004 or the databases 1006.Accordingly, the memory of processors 1010, the memory/storage devices1020, the peripheral devices 1004, and the databases 1006 are examplesof computer-readable and machine-readable media.

In some implementations, the electronic device(s), network(s),system(s), chip(s) or component(s), or portions or implementationsthereof, of FIGS. 1-10 perform one or more processes, techniques, ormethods as described herein, or portions thereof. FIG. 11 illustrates aflowchart of a process 1100 for SSB measurement accuracy testing. Insome implementations, the process 1100 is performed by one or more ofthe UEs 101. In other implementations, the process 1100 is performed byother electronic device(s) disclosed with respect to FIGS. 1-10 .

The process 1100 includes an UE receiving an SSB corresponding to afirst cell of a cellular communications network (1102). For example, oneof the UEs 101 receives a signal from one of the AN nodes 111 in the RAN110 of the system 100, the signal including an SSB of the correspondingcell. In some implementations, the UE 101 a receives an NR-SSS signalfrom the RAN node 111 a that is a gNB, the NR-SSS including an SSB forthe cell (e.g., cell 1) served by the gNB 111 a.

The process 1100 continues with the UE receiving an SSB corresponding toa second cell of the cellular communications network (1104). Forexample, in some implementations, the UE 101 a receives an NR-SSS signalfrom the RAN node 111 b that is a gNB, the NR-SSS including an SSB forthe cell (e.g., cell 2) served by the gNB 111 b.

The process 1100 continues with the UE clarifying the cell ID of thefirst cell (1106). For example, in some implementations, the UE 101 adetermines the cell ID of cell 1 served by the RAN node 111 a based onone or more PSS or SSS signals received from the RAN node 111 a.

The process 1100 continues with the UE clarifying the cell ID of thesecond cell (1108). For example, in some implementations, the UE 101 adetermines the cell ID of cell 2 served by the RAN node 111 b based onone or more PSS or SSS signals received from the RAN node 111 b.

The process 1100 continues with the UE determining an SSB measurementaccuracy value using respective cell IDs of the first cell and thesecond cell (1110). For example, in some implementations, the UE 101 adetermines a first RSRP for cell 1 served by the RAN node 111 a usingthe SSB received from the RAN node 111 a. The UE 101 a correlates thefirst RSRP to cell 1 using the cell ID of cell 1. The UE 101 adetermines a second RSRP for cell 2 served by the RAN node 111 b usingthe SSB received from the RAN node 111 b. The UE 101 a correlates thesecond RSRP to cell 2 using the cell ID of cell 2. The UE 101 a adjuststhe first RSRP and the second RSRP in response to correlating the firstRSRP to the cell 1 and the second RSRP to cell 2. The UE 101 adetermines the SSB measurement accuracy value using the adjusted firstRSRP and the second RSRP. In some implementations, the UE 101 adetermines, based on the SSB measurement accuracy value, whether toconnect to cell 1 or cell 2.

FIG. 12 illustrates a flowchart of a second process 1200 for SSBmeasurement accuracy testing. In some implementations, the process 1200is performed by one or more of the UEs 101. In other implementations,the process 1200 is performed by other electronic device(s) disclosedwith respect to FIGS. 1-10 .

The process 1200 includes an UE receiving a first signal in a first SMTCwindow corresponding to a first cell of a cellular communicationsnetwork, the first signal included in a first portion of the first SMTCwindow (1202). For example, one of the UEs 101 receives an NR-SSS signalin an SMTC window from one of the AN nodes 111 in the RAN 110 of thesystem 100. In some implementations, the UE 101 a receives an NR-SSSsignal from the RAN node 111 a that is a gNB, the NR-SSS included in afirst portion of an SMTC window for the cell (e.g., cell 1) served bythe gNB 111 a.

The process 1200 continues with the UE receiving a second signal in asecond SMTC window corresponding to a second cell of the cellularcommunications network, the second signal included in a second portionof the second SMTC window (1204). For example, in some implementations,the UE 101 a receives an NR-SSS signal from the RAN node 111 b that is agNB, the NR-SSS included in a second portion of an SMTC window for thecell (e.g., cell 2) served by the gNB 111 b. In some implementations,the first portion of the SMTC window for cell 1 does not overlap withthe second portion of the SMTC window for cell 2. For example, theNR-SSS for cell 1 can be sent in the first half of the SMTC window forcell 1, while the NR-SSS for cell 2 can be sent in the second half ofthe SMTC window for cell 2. Accordingly, even if the SMTC windows forcell 1 and cell 2 overlap in time (e.g., simultaneous SMTC windows foreach cell), the NR-SSS signals for the two cells do not overlap and thusdo not interfere with one another. In some implementations, the NR-SSSsignals for the two cells are time division multiplexed (TDM).

The process 1200 continues with the UE determining a first RSRP of thefirst cell using the first signal (1206). For example, in someimplementations, the UE 101 a obtains a first SSB for cell 1 from theNR-SSS for cell 1 received from the RAN node 111 a. The UE 101 adetermines a first RSRP of cell 1 using the first SSB.

The process 1200 continues with the UE determining a second RSRP of thesecond cell using the second signal (1208). For example, in someimplementations, the UE 101 a obtains a second SSB for cell 2 from theNR-SSS for cell 2 received from the RAN node 111 b. The UE 101 adetermines a second RSRP of cell 2 using the second SSB. The UE101 adetermines the first RSRP and the second RSRP independent of oneanother. In some implementations, upon determining the first RSRP forcell 1 and the second RSRP for cell 2, the UE 101 a determines whetherto connect to cell 1 or cell 2.

For one or more implementations, at least one of the components setforth in one or more of the preceding figures may be configured toperform one or more operations, techniques, processes, and/or methods asset forth in the example section below. For example, the basebandcircuitry as described above in connection with one or more of thepreceding figures may be configured to operate in accordance with one ormore of the examples set forth below. For another example, circuitryassociated with a UE, base station, network element, etc. as describedabove in connection with one or more of the preceding figures may beconfigured to operate in accordance with one or more of the examples setforth below in the example section.

It is to be noted that although process steps, method steps, algorithmsor the like may be described in a sequential order above, suchprocesses, methods and algorithms may generally be configured to work inalternate orders, unless specifically stated to the contrary.

The disclosed and other examples can be implemented as one or morecomputer program products, for example, one or more modules of computerprogram instructions encoded on a computer readable medium for executionby, or to control the operation of, data processing apparatus. Thecomputer readable medium can be a machine-readable storage device, amachine-readable storage substrate, a memory device, or a combination ofone or more them. The term “data processing apparatus” encompasses allapparatus, devices, and machines for processing data, including by wayof example a programmable processor, a computer, or multiple processorsor computers. The apparatus can include, in addition to hardware, codethat creates an execution environment for the computer program inquestion, e.g., code that constitutes processor firmware, a protocolstack, a database management system, an operating system, or acombination of one or more of them.

A system may encompass all apparatus, devices, and machines forprocessing data, including by way of example a programmable processor, acomputer, or multiple processors or computers. A system can include, inaddition to hardware, code that creates an execution environment for thecomputer program in question, e.g., code that constitutes processorfirmware, a protocol stack, a database management system, an operatingsystem, or a combination of one or more of them.

A computer program (also known as a program, software, softwareapplication, script, or code) can be written in any form of programminglanguage, including compiled or interpreted languages, and it can bedeployed in any form, including as a standalone program or as a module,component, subroutine, or other unit suitable for use in a computingenvironment. A computer program does not necessarily correspond to afile in a file system. A program can be stored in a portion of a filethat holds other programs or data (e.g., one or more scripts stored in amarkup language document), in a single file dedicated to the program inquestion, or in multiple coordinated files (e.g., files that store oneor more modules, sub programs, or portions of code). A computer programcan be deployed for execution on one computer or on multiple computersthat are located at one site or distributed across multiple sites andinterconnected by a communications network.

The processes and logic flows described in this document can beperformed by one or more programmable processors executing one or morecomputer programs to perform the functions described herein. Theprocesses and logic flows can also be performed by, and apparatus canalso be implemented as, special purpose logic circuitry, e.g., an FPGAor an ASIC (application specific integrated circuit).

Processors suitable for the execution of a computer program include, byway of example, both general and special purpose microprocessors, andany one or more processors of any kind of digital computer. Computerreadable media suitable for storing computer program instructions anddata can include all forms of nonvolatile memory, media and memorydevices. The processor and the memory can be supplemented by, orincorporated in, special purpose logic circuitry.

EXAMPLES

Example 1 may include a method for SSB measurement accuracy testingdesign, comprising: clarifying a Cell ID for cell 1 and cell.

Example 2 may include a method for SSB measurement accuracy testingdesign, comprising: when a cell ID need not be clarified, an NR-SSSsignal from cell 1 and cell 2 are TDM (time division multiplexed) to getrid of the impact of interference.

Example 3 may be a method for SSB measurement accuracy testing,comprising: clarifying a cell ID for a first cell; clarifying a cell IDfor a second cell; and determining, based upon the respective cell IDsfor the first cell and the second cell, an SSB measurement accuracyvalue.

Example 4 may include the method of example 3, or of any other exampleherein, further comprising determining whether to switch to the firstcell or the second cell based upon the determined SSB measurementaccuracy value.

Example 5 may be a method for SSB measurement accuracy testing,comprising: receiving a first signal from a first cell within an SMTCwindow; receiving a second signal from a second cell within the SMTCwindow; wherein the first signal is transmitted in a first portion ofthe SMTC window, and the second signal is transmitted in a secondportion of the SMTC window, wherein the first portion and the secondportion do not overlap; and based upon the received first signal and thereceived second signal, determine a SSB-based RSRP of the first cell andthe second cell.

Example 6 may include the method of example 5, or of any other exampleherein, wherein the SSB-based RSRP of the first cell or the SSB-basedRSRP of the second cell is determined independently.

Example 7 may include the method example 5, or of any other exampleherein, wherein the first signal or the second signal is a NR-SSSsignal.

Example 8 may include the method of example 7, or of any other exampleherein, wherein an NR-SSS signal from the first cell or the second cellare time division multiplexed.

Example 9 may include the method of any one of examples 4-8, furthercomprising determining whether to switch to the first cell or the secondcell based upon the determined SSB-based RSRP of the first cell and thesecond cell.

Example 10 may include an apparatus comprising means to perform one ormore elements of a method described in or related to any of examples1-9, or any other method or process described herein.

Example 11 may include one or more non-transitory computer-readablemedia comprising instructions to cause an electronic device, uponexecution of the instructions by one or more processors of theelectronic device, to perform one or more elements of a method describedin or related to any of examples 1-9, or any other method or processdescribed herein.

Example 12 may include an apparatus comprising logic, modules, orcircuitry to perform one or more elements of a method described in orrelated to any of examples 1-9, or any other method or process describedherein.

Example 13 may include a method, technique, or process as described inor related to any of examples 1-9, or portions or parts thereof.

Example 14 may include an apparatus comprising: one or more processorsand one or more computer-readable media comprising instructions that,when executed by the one or more processors, cause the one or moreprocessors to perform the method, techniques, or process as described inor related to any of examples 1-9, or portions thereof.

Example 15 may include a signal as described in or related to any ofexamples 1-9, or portions or parts thereof.

Example 16 may include a datagram, packet, frame, segment, protocol dataunit (PDU), or message as described in or related to any of examples1-9, or portions or parts thereof, or otherwise described in the presentdisclosure.

Example 17 may include a signal encoded with data as described in orrelated to any of examples 1-9, or portions or parts thereof, orotherwise described in the present disclosure.

Example 18 may include a signal encoded with a datagram, packet, frame,segment, protocol data unit (PDU), or message as described in or relatedto any of examples 1-9, or portions or parts thereof, or otherwisedescribed in the present disclosure.

Example 19 may include an electromagnetic signal carryingcomputer-readable instructions, wherein execution of thecomputer-readable instructions by one or more processors is to cause theone or more processors to perform the method, techniques, or process asdescribed in or related to any of examples 1-9, or portions thereof.

Example 20 may include a computer program comprising instructions,wherein execution of the program by a processing element is to cause theprocessing element to carry out the method, techniques, or process asdescribed in or related to any of examples 1-9, or portions thereof.

Example 21 may include a signal in a wireless network as shown anddescribed herein.

Example 22 may include a method of communicating in a wireless networkas shown and described herein.

Example 23 may include a system for providing wireless communication asshown and described herein.

Example 24 may include a device for providing wireless communication asshown and described herein.

Any of the above-described examples may be combined with any otherexample (or combination of examples), unless explicitly statedotherwise. The foregoing description of one or more implementationsprovides illustration and description, but is not intended to beexhaustive or to limit the scope of implementations to the precise formdisclosed. Modifications and variations are possible in light of theabove teachings or may be acquired from practice of variousimplementations.

Any of the above-described examples may be combined with any otherexample (or combination of examples), unless explicitly statedotherwise. The foregoing description of one or more implementationsprovides illustration and description, but is not intended to beexhaustive or to limit the scope of implementations to the precise formdisclosed. Modifications and variations are possible in light of theabove teachings or may be acquired from practice of variousimplementations.

While this document may describe many specifics, these should not beconstrued as limitations on the scope of an invention that is claimed orof what may be claimed, but rather as descriptions of features specificto particular implementations. Certain features that are described inthis document in the context of separate implementations can also beimplemented in combination in a single implementation. Conversely,various features that are described in the context of a singleimplementation can also be implemented in multiple implementationsseparately or in any suitable sub-combination. Moreover, althoughfeatures may be described above as acting in certain combinations andeven initially claimed as such, one or more features from a claimedcombination in some cases can be excised from the combination, and theclaimed combination may be directed to a sub-combination or a variationof a sub-combination. Similarly, while operations are depicted in thedrawings in a particular order, this should not be understood asrequiring that such operations be performed in the particular ordershown or in sequential order, or that all illustrated operations beperformed, to achieve desirable results.

Only a few examples and implementations are disclosed. Variations,modifications, and enhancements to the described examples andimplementations and other implementations can be made based on what isdisclosed.

Terminology

For the purposes of the present document, the following terms anddefinitions are applicable to the examples and implementations discussedherein.

The term “circuitry” as used herein refers to, is part of, or includeshardware components such as an electronic circuit, a logic circuit, aprocessor (shared, dedicated, or group) and/or memory (shared,dedicated, or group), an Application Specific Integrated Circuit (ASIC),a field-programmable device (FPD) (e.g., a field-programmable gate array(FPGA), a programmable logic device (PLD), a complex PLD (CPLD), ahigh-capacity PLD (HCPLD), a structured ASIC, or a programmable SoC),digital signal processors (DSPs), etc., that are configured to providethe described functionality. In some implementations, the circuitry mayexecute one or more software or firmware programs to provide at leastsome of the described functionality. The term “circuitry” may also referto a combination of one or more hardware elements (or a combination ofcircuits used in an electrical or electronic system) with the programcode used to carry out the functionality of that program code. In theseimplementations, the combination of hardware elements and program codemay be referred to as a particular type of circuitry.

The term “processor circuitry” as used herein refers to, is part of, orincludes circuitry capable of sequentially and automatically carryingout a sequence of arithmetic or logical operations, or recording,storing, and/or transferring digital data. The term “processorcircuitry” may refer to one or more application processors, one or morebaseband processors, a physical central processing unit (CPU), asingle-core processor, a dual-core processor, a triple-core processor, aquad-core processor, and/or any other device capable of executing orotherwise operating computer-executable instructions, such as programcode, software modules, and/or functional processes. The terms“application circuitry” and/or “baseband circuitry” may be consideredsynonymous to, and may be referred to as, “processor circuitry.”

The term “interface circuitry” as used herein refers to, is part of, orincludes circuitry that enables the exchange of information between twoor more components or devices. The term “interface circuitry” may referto one or more hardware interfaces, for example, buses, I/O interfaces,peripheral component interfaces, network interface cards, and/or thelike.

The term “user equipment” or “UE” as used herein refers to a device withradio communication capabilities and may describe a remote user ofnetwork resources in a communications network. The term “user equipment”or “UE” may be considered synonymous to, and may be referred to as,client, mobile, mobile device, mobile terminal, user terminal, mobileunit, mobile station, mobile user, subscriber, user, remote station,access agent, user agent, receiver, radio equipment, reconfigurableradio equipment, reconfigurable mobile device, etc. Furthermore, theterm “user equipment” or “UE” may include any type of wireless/wireddevice or any computing device including a wireless communicationsinterface.

The term “network element” as used herein refers to physical orvirtualized equipment and/or infrastructure used to provide wired orwireless communication network services. The term “network element” maybe considered synonymous to and/or referred to as a networked computer,networking hardware, network equipment, network node, router, switch,hub, bridge, radio network controller, RAN device, RAN node, gateway,server, virtualized VNF, NFVI, and/or the like.

The term “computer system” as used herein refers to any typeinterconnected electronic devices, computer devices, or componentsthereof. Additionally, the term “computer system” and/or “system” mayrefer to various components of a computer that are communicativelycoupled with one another. Furthermore, the term “computer system” and/or“system” may refer to multiple computer devices and/or multiplecomputing systems that are communicatively coupled with one another andconfigured to share computing and/or networking resources.

The term “appliance,” “computer appliance,” or the like, as used hereinrefers to a computer device or computer system with program code (e.g.,software or firmware) that is specifically designed to provide aspecific computing resource. A “virtual appliance” is a virtual machineimage to be implemented by a hypervisor-equipped device that virtualizesor emulates a computer appliance or otherwise is dedicated to provide aspecific computing resource.

The term “resource” as used herein refers to a physical or virtualdevice, a physical or virtual component within a computing environment,and/or a physical or virtual component within a particular device, suchas computer devices, mechanical devices, memory space, processor/CPUtime, processor/CPU usage, processor and accelerator loads, hardwaretime or usage, electrical power, input/output operations, ports ornetwork sockets, channel/link allocation, throughput, memory usage,storage, network, database and applications, workload units, and/or thelike. A “hardware resource” may refer to compute, storage, and/ornetwork resources provided by physical hardware element(s). A“virtualized resource” may refer to compute, storage, and/or networkresources provided by virtualization infrastructure to an application,device, system, etc. The term “network resource” or “communicationresource” may refer to resources that are accessible by computerdevices/systems via a communications network. The term “systemresources” may refer to any kind of shared entities to provide services,and may include computing and/or network resources. System resources maybe considered as a set of coherent functions, network data objects orservices, accessible through a server where such system resources resideon a single host or multiple hosts and are clearly identifiable.

The term “channel” as used herein refers to any transmission medium,either tangible or intangible, which is used to communicate data or adata stream. The term “channel” may be synonymous with and/or equivalentto “communications channel,” “data communications channel,”“transmission channel,” “data transmission channel,” “access channel,”“data access channel,” “link,” “data link,” “carrier,” “radiofrequencycarrier,” and/or any other like term denoting a pathway or mediumthrough which data is communicated. Additionally, the term “link” asused herein refers to a connection between two devices through a RAT forthe purpose of transmitting and receiving information.

The terms “instantiate,” “instantiation,” and the like as used hereinrefers to the creation of an instance. An “instance” also refers to aconcrete occurrence of an object, which may occur, for example, duringexecution of program code.

The terms “coupled,” “communicatively coupled,” along with derivativesthereof are used herein. The term “coupled” may mean two or moreelements are in direct physical or electrical contact with one another,may mean that two or more elements indirectly contact each other butstill cooperate or interact with each other, and/or may mean that one ormore other elements are coupled or connected between the elements thatare said to be coupled with each other. The term “directly coupled” maymean that two or more elements are in direct contact with one another.The term “communicatively coupled” may mean that two or more elementsmay be in contact with one another by a means of communication includingthrough a wire or other interconnect connection, through a wirelesscommunication channel or ink, and/or the like.

The term “information element” refers to a structural element containingone or more fields. The term “field” refers to individual contents of aninformation element, or a data element that contains content.

The term “SMTC” refers to an SSB-based measurement timing configurationconfigured by SSB-MeasurementTimingConfiguration.

The term “SSB” refers to an SS/PBCH block.

The term “a “Primary Cell” refers to the MCG cell, operating on theprimary frequency, in which the UE either performs the initialconnection establishment procedure or initiates the connectionre-establishment procedure.

The term “Primary SCG Cell” refers to the SCG cell in which the UEperforms random access when performing the Reconfiguration with Syncprocedure for dual connectivity operation.

The term “Secondary Cell” refers to a cell providing additional radioresources on top of a Special Cell for a UE configured with CA.

The term “Secondary Cell Group” refers to the subset of serving cellscomprising the PSCell and zero or more secondary cells for a UEconfigured with DC.

The term “Serving Cell” refers to the primary cell for a UE inRRC_CONNECTED not configured with CA/DC there is only one serving cellcomprising of the primary cell.

The term “serving cell” or “serving cells” refers to the set of cellscomprising the Special Cell(s) and all secondary cells for a UE inRRC_CONNECTED configured with CA/.

The term “Special Cell” refers to the PCell of the MCG or the PSCell ofthe SCG for dual connectivity operation; otherwise, the term “SpecialCell” refers to the Pcell.

What is claimed is:
 1. A method comprising: receiving, at a userequipment (UE) in a cellular communications network, a firstSynchronization Signal Block (SSB) corresponding to a first cell of thecellular communications network, and a second SSB corresponding to asecond cell of the cellular communications network; clarifying, by theUE, a first cell identifier (ID) of the first cell; clarifying, by theUE, a second cell ID of the second cell; and determining, by the UEusing the first cell ID and the second cell ID, an SSB measurementaccuracy value.
 2. The method of claim 1, wherein clarifying the firstcell ID of the first cell and the second cell ID of the second cellcomprises: determining, by the UE, the first cell ID using one or morefirst signals received from a first base station corresponding to thefirst cell; and determining, by the UE, the second cell ID using one ormore second signals received from a second base station corresponding tothe second cell.
 3. The method of claim 2, wherein the one or more firstsignals include one or more of a Primary Synchronization Signal (PSS) ora Secondary Synchronization Signal (SSS) received from the first basestation, and wherein the one or more second signals include one or moreof a PSS or an SSS received from the second base station.
 4. The methodof claim 2, wherein the first base station includes one of an evolvedNodeB (eNB) or a Next Generation NodeB (gNB), and wherein the secondbase station includes one of an eNB or a gNB.
 5. The method of claim 1,wherein determining the SSB measurement accuracy value comprises:measuring a first Reference Signal Received Power (RSRP) for the firstcell; correlating the first RSRP to the first cell using the first cellID; measuring a second RSRP for the second cell; correlating the secondRSRP to the second cell using the second cell ID; adjusting the firstRSRP and the second RSRP in response to correlating the first RSRP tothe first cell and the second RSRP to the second cell; and determiningthe SSB measurement accuracy value using the adjusted first RSRP and thesecond RSRP.
 6. The method of claim 1, wherein receiving the first SSBcomprises receiving a first New Radio Secondary Synchronization Signal(NR-SSS) corresponding to the first cell, and wherein receiving thesecond SSB comprises receiving a second NR-SSS corresponding to thesecond cell.
 7. The method of claim 1, further comprising: determining,by the UE, whether to connect to the first cell or the second cell basedon the SSB measurement accuracy value.
 8. A method comprising:receiving, at a user equipment (UE) in a cellular communicationsnetwork, a first signal in a first SSB-based Measurement TimingConfiguration (SMTC) window corresponding to a first cell of thecellular communications network, the first signal included in a firstportion of the first SMTC window; receiving, at the UE, a second signalin a second SMTC window corresponding to a second cell of the cellularcommunications network, the second signal included in a second portionof the second SMTC window, wherein the second portion of the second SMTCwindow does not overlap with the first portion of the first SMTC window;determining, by the UE, a first Reference Signal Received Power (RSRP)for the first cell using the first signal; and determining, by the UE, asecond RSRP for the second cell using the second signal.
 9. The methodof claim 8, wherein receiving the first signal in the first SMTC windowcomprises receiving a New Radio Secondary Synchronization Signal(NR-SSS) in the first SMTC window.
 10. The method of claim 8, whereinreceiving the second signal in the second SMTC window comprisesreceiving a NR-SSS in the second SMTC window.
 11. The method of claim 8,wherein receiving the first signal in the first SMTC window comprisesobtaining a first Synchronization Signal Block (SSB) corresponding tothe first cell from the first signal, and wherein determining the firstRSRP for the first cell comprises determining an SSB-based RSRP for thefirst cell.
 12. The method of claim 8, wherein receiving the secondsignal in the second SMTC window comprises obtaining a second SSBcorresponding to the second cell from the second signal, and whereindetermining the second RSRP for the second cell comprises determining anSSB-based RSRP for the second cell.
 13. The method of claim 8, whereindetermining the first RSRP and the second RSRP comprises determining thefirst RSRP and the second RSRP independent of one another.
 14. Themethod of claim 8, wherein the first signal from the first cell is timedivision multiplexed (TDM) with the second signal from the second cell.15. The method of claim 8, further comprising: determining, by the UE,whether to connect to the first cell or the second cell based on thefirst RSRP and the second RSRP.
 16. The method of claim 8, whereinreceiving the first signal comprises receiving the first signal from afirst base station corresponding to the first cell, and whereinreceiving the second signal comprises receiving the second signal from asecond base station corresponding to the second cell.
 17. The method ofclaim 16, wherein the first base station includes one of an evolvedNodeB (eNB) or a Next Generation NodeB (gNB), and wherein the secondbase station includes one of an eNB or a gNB.
 18. One or morenon-transitory computer-readable media storing instructions that, whenexecuted by one or more processors, are configured to cause the one ormore processors to perform operations comprising: receiving, at a userequipment (UE) in a cellular communications network, a firstSynchronization Signal Block (SSB) corresponding to a first cell of thecellular communications network, and a second SSB corresponding to asecond cell of the cellular communications network; clarifying, by theUE, a first cell identifier (ID) of the first cell; clarifying, by theUE, a second cell ID of the second cell; and determining, by the UEusing the first cell ID and the second cell ID, an SSB measurementaccuracy value.
 19. The one or more non-transitory computer-readablemedia of claim 18, wherein clarifying the first cell ID of the firstcell and the second cell ID of the second cell comprises: determining,by the UE, the first cell ID using one or more first signals receivedfrom a first base station corresponding to the first cell; anddetermining, by the UE, the second cell ID using one or more secondsignals received from a second base station corresponding to the secondcell.
 20. The one or more non-transitory computer-readable media ofclaim 19, wherein the one or more first signals include one or more of aPrimary Synchronization Signal (PSS) or a Secondary SynchronizationSignal (SSS) received from the first base station, and wherein the oneor more second signals include one or more of a PSS or an SSS receivedfrom the second base station.
 21. The one or more non-transitorycomputer-readable media of claim 19, wherein the first base stationincludes one of an evolved NodeB (eNB) or a Next Generation NodeB (gNB),and wherein the second base station includes one of an eNB or a gNB. 22.The one or more non-transitory computer-readable media of claim 18,wherein determining the SSB measurement accuracy value comprises:measuring a first Reference Signal Received Power (RSRP) for the firstcell; correlating the first RSRP to the first cell using the first cellID; measuring a second RSRP for the second cell; correlating the secondRSRP to the second cell using the second cell ID; adjusting the firstRSRP and the second RSRP in response to correlating the first RSRP tothe first cell and the second RSRP to the second cell; and determiningthe SSB measurement accuracy value using the adjusted first RSRP and thesecond RSRP.
 23. The one or more non-transitory computer-readable mediaof claim 18, wherein receiving the first SSB comprises receiving a firstNew Radio Secondary Synchronization Signal (NR-SSS) corresponding to thefirst cell, and wherein receiving the second SSB comprises receiving asecond NR-SSS corresponding to the second cell.
 24. The one or morenon-transitory computer-readable media of claim 18, wherein theoperations further comprise: determining, by the UE, whether to connectto the first cell or the second cell based on the SSB measurementaccuracy value.
 25. One or more non-transitory computer-readable mediastoring instructions that, when executed by one or more processors, areconfigured to cause the one or more processors to perform operationscomprising: receiving, at a user equipment (UE) in a cellularcommunications network, a first signal in a first SSB-based MeasurementTiming Configuration (SMTC) window corresponding to a first cell of thecellular communications network, the first signal included in a firstportion of the first SMTC window; receiving, at the UE, a second signalin a second SMTC window corresponding to a second cell of the cellularcommunications network, the second signal included in a second portionof the second SMTC window, wherein the second portion of the second SMTCwindow does not overlap with the first portion of the first SMTC window;determining, by the UE, a first Reference Signal Received Power (RSRP)for the first cell using the first signal; and determining, by the UE, asecond RSRP for the second cell using the second signal.
 26. The one ormore non-transitory computer-readable media of claim 25, whereinreceiving the first signal in the first SMTC window comprises receivinga New Radio Secondary Synchronization Signal (NR-SSS) in the first SMTCwindow.
 27. The one or more non-transitory computer-readable media ofclaim 25, wherein receiving the second signal in the second SMTC windowcomprises receiving a NR-SSS in the second SMTC window.
 28. The one ormore non-transitory computer-readable media of claim 25, whereinreceiving the first signal in the first SMTC window comprises obtaininga first Synchronization Signal Block (SSB) corresponding to the firstcell from the first signal, and wherein determining the first RSRP forthe first cell comprises determining an SSB-based RSRP for the firstcell.
 29. The one or more non-transitory computer-readable media ofclaim 25, wherein receiving the second signal in the second SMTC windowcomprises obtaining a second SSB corresponding to the second cell fromthe second signal, and wherein determining the second RSRP for thesecond cell comprises determining an SSB-based RSRP for the second cell.30. The one or more non-transitory computer-readable media of claim 25,wherein determining the first RSRP and the second RSRP comprisesdetermining the first RSRP and the second RSRP independent of oneanother.
 31. The one or more non-transitory computer-readable media ofclaim 25, wherein the first signal from the first cell is time divisionmultiplexed (TDM) with the second signal from the second cell.
 32. Theone or more non-transitory computer-readable media of claim 25, furthercomprising: determining, by the UE, whether to connect to the first cellor the second cell based on the first RSRP and the second RSRP.
 33. Theone or more non-transitory computer-readable media of claim 25, whereinreceiving the first signal comprises receiving the first signal from afirst base station corresponding to the first cell, and whereinreceiving the second signal comprises receiving the second signal from asecond base station corresponding to the second cell.
 34. The one ormore non-transitory computer-readable media of claim 33, wherein thefirst base station includes one of an evolved NodeB (eNB) or a NextGeneration NodeB (gNB), and wherein the second base station includes oneof an eNB or a gNB.
 35. An apparatus comprising: one or more processors;and one or more computer-readable media storing instructions that, whenexecuted by the one or more processors, are configured to cause the oneor more processors to perform operations comprising: receiving, at auser equipment (UE) in a cellular communications network, a firstSynchronization Signal Block (SSB) corresponding to a first cell of thecellular communications network, and a second SSB corresponding to asecond cell of the cellular communications network; clarifying, by theUE, a first cell identifier (ID) of the first cell; clarifying, by theUE, a second cell ID of the second cell; and determining, by the UEusing the first cell ID and the second cell ID, an SSB measurementaccuracy value.
 36. The apparatus of claim 35, wherein clarifying thefirst cell ID of the first cell and the second cell ID of the secondcell comprises: determining, by the UE, the first cell ID using one ormore first signals received from a first base station corresponding tothe first cell; and determining, by the UE, the second cell ID using oneor more second signals received from a second base station correspondingto the second cell.
 37. The apparatus of claim 36, wherein the one ormore first signals include one or more of a Primary SynchronizationSignal (PSS) or a Secondary Synchronization Signal (SSS) received fromthe first base station, and wherein the one or more second signalsinclude one or more of a PSS or an SSS received from the second basestation.
 38. The apparatus of claim 36, wherein the first base stationincludes one of an evolved NodeB (eNB) or a Next Generation NodeB (gNB),and wherein the second base station includes one of an eNB or a gNB. 39.The apparatus of claim 35, wherein determining the SSB measurementaccuracy value comprises: measuring a first Reference Signal ReceivedPower (RSRP) for the first cell; correlating the first RSRP to the firstcell using the first cell ID; measuring a second RSRP for the secondcell; correlating the second RSRP to the second cell using the secondcell ID; adjusting the first RSRP and the second RSRP in response tocorrelating the first RSRP to the first cell and the second RSRP to thesecond cell; and determining the SSB measurement accuracy value usingthe adjusted first RSRP and the second RSRP.
 40. The apparatus of claim35, wherein receiving the first SSB comprises receiving a first NewRadio Secondary Synchronization Signal (NR-SSS) corresponding to thefirst cell, and wherein receiving the second SSB comprises receiving asecond NR-SSS corresponding to the second cell.
 41. The apparatus ofclaim 35, wherein the operations further comprise: determining, by theUE, whether to connect to the first cell or the second cell based on theSSB measurement accuracy value.
 42. An apparatus comprising: one or moreprocessors; and one or more computer-readable media storing instructionsthat, when executed by the one or more processors, are configured tocause the one or more processors to perform operations comprising:receiving, at a user equipment (UE) in a cellular communicationsnetwork, a first signal in a first SSB-based Measurement TimingConfiguration (SMTC) window corresponding to a first cell of thecellular communications network, the first signal included in a firstportion of the first SMTC window; receiving, at the UE, a second signalin a second SMTC window corresponding to a second cell of the cellularcommunications network, the second signal included in a second portionof the second SMTC window, wherein the second portion of the second SMTCwindow does not overlap with the first portion of the first SMTC window;determining, by the UE, a first Reference Signal Received Power (RSRP)for the first cell using the first signal; and determining, by the UE, asecond RSRP for the second cell using the second signal.
 43. Theapparatus of claim 42, wherein receiving the first signal in the firstSMTC window comprises receiving a New Radio Secondary SynchronizationSignal (NR-SSS) in the first SMTC window.
 44. The apparatus of claim 42,wherein receiving the second signal in the second SMTC window comprisesreceiving a NR-SSS in the second SMTC window.
 45. The apparatus of claim42, wherein receiving the first signal in the first SMTC windowcomprises obtaining a first Synchronization Signal Block (SSB)corresponding to the first cell from the first signal, and whereindetermining the first RSRP for the first cell comprises determining anSSB-based RSRP for the first cell.
 46. The apparatus of claim 42,wherein receiving the second signal in the second SMTC window comprisesobtaining a second SSB corresponding to the second cell from the secondsignal, and wherein determining the second RSRP for the second cellcomprises determining an SSB-based RSRP for the second cell.
 47. Theapparatus of claim 42, wherein determining the first RSRP and the secondRSRP comprises determining the first RSRP and the second RSRPindependent of one another.
 48. The apparatus of claim 42, wherein thefirst signal from the first cell is time division multiplexed (TDM) withthe second signal from the second cell.
 49. The apparatus of claim 42,further comprising: determining, by the UE, whether to connect to thefirst cell or the second cell based on the first RSRP and the secondRSRP.
 50. The apparatus of claim 42, wherein receiving the first signalcomprises receiving the first signal from a first base stationcorresponding to the first cell, and wherein receiving the second signalcomprises receiving the second signal from a second base stationcorresponding to the second cell.
 51. The apparatus of claim 50, whereinthe first base station includes one of an evolved NodeB (eNB) or a NextGeneration NodeB (gNB), and wherein the second base station includes oneof an eNB or a gNB.